Lines Matching full:users

5 compatibility with previous versions, so users (and alt implementers) might
78 The change affects users who use any of the following functions:
92 This change does not affect users who use the default configuration; it only
93 affects users who enabled that option.
125 This does not affect users who use the default `mbedtls_config.h`, as this option was
139 This only affects users who called the HAVEGE modules directly (not
140 recommended), or users who used it through the entropy module but had it as the
211 This does not affect users who use the default `mbedtls_config.h`. `MBEDTLS_SHA256_C`
222 This does not affect users who use the default `mbedtls_config.h`.
256 This doesn't affect users of the default configuration; it only affects people
287 This affects all users who use the RSA encrypt, decrypt, sign and
320 This change affects users who were using the `mbedtls_*_ret()` cryptography
365 This affects all users who use the RSA encrypt, decrypt, sign and
421 This change affects users of the MD2, MD4, RC4, Blowfish and XTEA algorithms.
424 those reasons possible users should consider switching to modern and safe
446 This affects users of the PK API as well as users of the low-level API in the RSA module. Users of …
479 This change affects all users who called a function accepting a `f_rng`
495 `f_rng` argument but must allow users to pass one anyway.
499 This affects users of the following functions: `mbedtls_ecp_check_pub_priv()`,
521 This shouldn't affect users who took care not to include headers that
565 This change does not affect users of the default configuration; it only affects
566 users who enable this option.
582 This change affects users who have chosen the configuration options to disable the
600 This change does not affect users who were using the default configuration, as
601 this option was already disabled by default. Also, it does not affect users who
631 This change affects users of the TLS 1.0, 1.1 and DTLS 1.0 protocols.
661 This only affects TLS users who explicitly enabled `MBEDTLS_SSL_PROTO_SSL3`
678 This affects users of truncated HMAC, that is, users who called
691 This only affects TLS users who enabled `MBEDTLS_ZLIB_SUPPORT`. This will not
735 This change affects users who modified the default `mbedtls_config.h` padding granularity
755 This affects users of the SSL key export APIs:
766   SSL context. This allows users to more easily identify the
777 For users which do not rely on raw keys and IV, adjusting to the new
782 Users which require access to the raw keys used to secure application
785 on the wire. Such users are also encouraged to reach out to the
791 This affects users which use the MFL query APIs
796 Users should switch to `mbedtls_ssl_get_max_{in,out}_record_payload()`
802 This affects users which call the PSK configuration APIs
806 In Mbed TLS 2.x, users would observe later calls overwriting
813 users calling `mbedtls_ssl_conf_[opaque_]psk()` multiple times should
820 This does not affect users who use the default `mbedtls_config.h`, as this option was
832 This affects users who use the `MBEDTLS_SSL_MAX_CONTENT_LEN` option to
842 This affects two classes of users:
844 1. Users who manually inspect parts of the current session through
847 2. Users of session resumption who query the current session
859 2. Users should replace calls to `mbedtls_ssl_get_session_pointer()` by
865 This change does not affect users who used the default `mbedtls_config.h`, as the option
869 users who didn't need that feature to avoid paying the cost in code size, by
886 This change does not affect users who use the default `mbedtls_config.h`, as the
891 was made optional to allow users who don't need it to save some code space.
894 Users who changed the default setting of the option need to change the config/
899 This affects users who use `mbedtls_ssl_conf_session_cache()`
903 Those users will need to modify the API of their session cache
920 `mbedtls_ssl_session`. See the corresponding migration guide. Users that
927 This affects users manually checking for the following error codes:
941   Users should check for `MBEDTLS_ERR_SSL_BUFFER_TOO_SMALL` instead, and potentially
950   Users should check for the newly introduced generic error codes
970 This affects users who call `mbedtls_ssl_get_session()` or
973 Those users will now observe the second call to fail with
1000 This change affects users who were enabling `MBEDTLS_SSL_SRV_RESPECT_CLIENT_PREFERENCE`
1032 This change does not affect users using default settings for 3DES in `mbedtls_config.h`