File not found: iperf-3.16.tar.gz.sha256

A Tool To Measure Network Performance

Edit Package iperf

Iperf was developed by NLANR/DAST as a modern alternative for
measuring maximum TCP and UDP bandwidth performance.
Iperf allows the tuning of various parameters and UDP characteristics.
Iperf reports bandwidth, delay jitter, datagram loss.

Refresh
Refresh
Source Files
Filename Size Changed
iperf-3.17.1.tar.gz 0000670547 655 KB
iperf-3.17.1.tar.gz.sha256 0000000086 86 Bytes
iperf.changes 0000022833 22.3 KB
iperf.spec 0000003636 3.55 KB
Latest Revision
Ana Guerrero's avatar Ana Guerrero (anag+factory) accepted request 1174204 from Dirk Mueller's avatar Dirk Mueller (dirkmueller) (revision 38)
- update to 3.17.1 (bsc#1224262, CVE-2024-26306):
  * BREAKING CHANGE: iperf3's authentication features, when used
    with OpenSSL prior to 3.2.0, contain a vulnerability to a
    side-channel timing attack. To address this flaw, a change
    has been made to the padding applied to encrypted strings.
    This change is not backwards compatible with older versions of
    iperf3 (before 3.17). To restore
    the older (vulnerable) behavior, and hence
    backwards-compatibility, use the --use-pkcs1-padding flag. The
    iperf3 team thanks Hubert Kario from RedHat for reporting this
    issue and providing feedback on the fix. (CVE-2024-26306)(PR#1695)
  * iperf3 no longer changes its current working directory in --daemon
    mode. This results in more predictable behavior with relative
    paths, in particular finding key and credential files for
    authentication. (PR#1672)
  * A new --json-stream option has been added to enable a streaming
    output format, consisting of a series of JSON objects (for the
    start of the test, each measurement interval, and the end of the
    test) separated by newlines (#444, #923, #1098).
  * UDP tests now work correctly between different endian hosts
  * The --fq-rate parameter now works for --reverse tests
  * The statistics reporting interval is now available in the --json
    start test object (#1663).
  * A negative time test duration is now properly flagged as an error
    (IS#1662 / PR#1666).
Comments 0
openSUSE Build Service is sponsored by