Releases: tinyboxvk/iperf-windows-builds
3.18
3.18 (2024-05-13, 2a29844)
-
Notable user-visible changes
-
SECURITY NOTE: Thanks to Leonid Krolle Bi.Zone for discovering a
JSON type security vulnerability that caused a
segmentation fault in the
server. (CVE-2024-53580) This has now been
fixed. (PR#1810) -
UDP packets per second now reports the correct number of
packets, by reporting NET_SOFTERROR if there's a EAGAIN/EINTR
errno if no data was sent (esnet#1367/PR#1379). -
Several segmentation faults related to threading were fixed. One
where pthread_cancel was called on an improperly initialized
thread (esnet#1801), another where threads were being recycled
(esnet#1760/PR#1761), and another where threads were improperly
handling signals (esnet#1750/PR#1752). -
A segmentation fault from calling freeaddrinfo with NULL was
fixed (PR#1755). -
Some JSON options were fixed, including checking the size for
json_read (PR#1709), but the size limit was removed for
received server output (PR#1779). -
A rcv-timeout error has been fixed. The Nread timeout was
hardcoded and timed out before the --rcv-timeout option
(PR#1744). -
There is no longer a limit on the omit time period
(esnet#1770/PR#1774). -
Fixed an output crash under 32-bit big-endian systems (PR#1713).
-
An issue was fixed where CPU utilization was unexpectedly high
during limited baud rate tests. The --pacing-timer option was
removed, but it is still available in the library
(esnet#1741/PR#1743). -
Add SCTP information to --json output and fixed compile error
when SCTP is not supported (esnet#1731) -
--fq-rate was changed from a uint to a uint64 to allow pacing above
32G. Not yet tested on big-endian systems (PR#1728).
-
-
Notable developer-visible changes
-
Clang compilation failure on Android were fixed (PR#1687).
-
iperf_time_add() was optimizated to improve performance
(PR#1742). -
Debug messages were added when the state changes (PR#1734).
-
To increase performance, the old UDP prot_listener is cleared
and removed after each test (PR#1708). -
A file descriptor leak was closed (PR#1619).
-
3.17.1
3.17
3.17 (2024-05-10, 2a23508)
-
Notable user-visible changes
-
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 (esnet#444, esnet#923, esnet#1098). -
UDP tests now work correctly between different endian hosts
(esnet#1415). -
The --fq-rate parameter now works for --reverse tests (esnet#1632, PR#1667).
-
The statistics reporting interval is now available in the --json
start test object (esnet#1663). -
A negative time test duration is now properly flagged as an error
(IS#1662 / PR#1666).
-
-
Notable developer-visible changes
-
Fixes have been made to better (unofficially) support builds on
Android (esnet#1641 / esnet#1651) and VxWorks (esnet#1595). -
iperf3 now builds correctly on architectures without native
support for 64-bit atomic types, by linking with the libatomic
library (esnet#1611).
-
3.16
3.16 (2023-12-01, f9481e1)
-
Notable user-visible changes
-
Multiple test streams started with -P/--parallel will now be
serviced by different threads. This allows iperf3 to take
advantage of multiple CPU cores on modern processors, and will
generally result in significant throughput increases (PR esnet#1591). -
OpenSSL 3 is now detected at build time. If OpenSSL 3 is found,
various older, deprecated, APIs will not be used. iperf3 will
continue to work with OpenSSL 1.1.1. OpenSSL is used as a part
of the iperf3 authentication functionality (Issue esnet#1300, PR
esnet#1589). -
The authorized users file used by the authentication functionality
is now checked for accessibility much earlier during the program
startup, as opposed to being checked near the start of a
test (Issue esnet#1583, PR esnet#1585).
-
-
Developer-visible changes
- BREAKING CHANGE: iperf3 now requires pthreads and C atomic
variables to compile and run.
- BREAKING CHANGE: iperf3 now requires pthreads and C atomic