mirror of
https://github.com/Mbed-TLS/mbedtls.git
synced 2025-07-28 00:21:48 +03:00
Change wording in documentation of PSK configuration
Signed-off-by: Hanno Becker <hanno.becker@arm.com>
This commit is contained in:
@ -7,17 +7,12 @@ multiple times on the same SSL configuration.
|
||||
|
||||
In Mbed TLS 2.x, users would observe later calls overwriting
|
||||
the effect of earlier calls, with the prevailing PSK being
|
||||
the one that has been configured last.
|
||||
the one that has been configured last. In Mbed TLS 3.0,
|
||||
calling `mbedtls_conf_[opaque_]psk()` multiple times
|
||||
will return an error, leaving the first PSK intact.
|
||||
|
||||
To achieve equivalent functionality when migrating to Mbed TLS 3.0,
|
||||
users calling `mbedtls_ssl_conf_[opaque_]psk()` multiple times should
|
||||
remove all but the last call, so that only one call to _either_
|
||||
`mbedtls_ssl_conf_psk()` _or_ `mbedtls_ssl_conf_psk_opaque()`
|
||||
remains.
|
||||
|
||||
However, if the _intent_ of the multiple calls to
|
||||
`mbedtls_ssl_conf_[opaque_]psk()` was to offer multiple PSKs, then
|
||||
users should _keep_ all calls and only check for the expected
|
||||
non-fatal failure code `MBEDTLS_ERR_SSL_FEATURE_UNAVAILABLE`
|
||||
indicating that no more PSKs could be buffered by the
|
||||
implementation.
|
||||
|
Reference in New Issue
Block a user