|
Revision tags: 3.11, 3.10.1, 3.10 |
|
| #
bd143779 |
| 12-Nov-2020 |
ralcini <[email protected]> |
Configurable value for time drift between client/server for authentication request issue1065 (#1070)
* Issue 1065
* feat: Allow to configure a custom value for time drift between client/server fo
Configurable value for time drift between client/server for authentication request issue1065 (#1070)
* Issue 1065
* feat: Allow to configure a custom value for time drift between client/server for authentication
The use case is to support scenarios where it's not possible to enforce sync between client and server times.
* enh: drift redefined with skew
Co-authored-by: Francesco Marino <[email protected]>
show more ...
|
|
Revision tags: 3.9, 3.8.1, 3.8 |
|
| #
22da02dc |
| 01-Oct-2019 |
Allen Flickinger <[email protected]> |
enh: Add server authentication API functions (#911)
|
|
Revision tags: 3.7, 3.6 |
|
| #
e28f12c7 |
| 27-Apr-2018 |
ralcini <[email protected]> |
Add authentication functions to libiperf (#713)
Fixes #712. A subsequent commit will add some information to the libiperf manual page.
|
|
Revision tags: 3.5, 3.4, 3.3, 3.2, 3.2rc1 |
|
| #
a51045de |
| 20-Apr-2017 |
ralcini <[email protected]> |
Service Authentication (#517)
Add an optional mode that requires clients to authenticate with the server.
In this mode, clients need to provide a username and a password, which are checked agains
Service Authentication (#517)
Add an optional mode that requires clients to authenticate with the server.
In this mode, clients need to provide a username and a password, which are checked against a password file on the server. The authentication credentials are protected by an RSA public keypair...the encrypted credentials are sent along with the test parameters.
Operationally the use of this feature places the following additional requirements on the build and installation of iperf3:
o The presence of the OpenSSL headers and libraries to build iperf3, and the libraries available on the client and server at runtime.
o Generation of an RSA public keypair; the private part is used by the server and the public part must be distributed to the clients.
o Username/password pairs for all authorized users, to be stored in a file on the server.
o Loose time synchronization between the server and clients (to within approximately 30 seconds).
o Appropriate command-line flags given on the client and server.
Note that iperf3 can be built and run as before, without fulfilling any of these requirements.
Partial documentation for this feature is included in this commit. It is anticipated that additional documentation text and editing will follow this merge.
Submitted by @ralcini. First suggested by @codyhanson in pull request #242.
show more ...
|