Lines Matching refs:not
25 migration path is not provided in prior documentation, changes made and the
34 suffixed with `_ret`. In Mbed TLS 3.x, this change may not be required, as most
64 …headers is no longer supported. In Mbed TLS 3, the layout of structures is not considered part of …
70 If you were accessing structure fields directly, and these fields are not documented as public, you…
92 This change does not affect users who use the default configuration; it only
99 that the pointer is non-null. With the feature disabled, a null pointer is not
111 not used in X.509, TLS or in PSA crypto, and it was not implemented in all
118 Validation of enum-like values is somewhat useful, but not extremely important,
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
179 removed. The primes from RFC 5114 are deprecated because their derivation is not
202 not increase peak RAM usage anymore.
211 This does not affect users who use the default `mbedtls_config.h`. `MBEDTLS_SHA256_C`
217 Current version of the library does not support enabling `MBEDTLS_SHA256_C`
222 This does not affect users who use the default `mbedtls_config.h`.
236 … or using GCM via the `mbedtls_cipher_xxx` or `psa_aead_xxx` interfaces do not require any changes.
241 …* If the length of the last input is not a multiple of 16, alternative implementations may return …
250 …* Always return the partial output immediately, even if it does not consist of a whole number of b…
442 The requirements for the output buffer have not changed, but passing a buffer that is too small now…
521 This shouldn't affect users who took care not to include headers that
547 This should not affect production use of the library, as the certificates and
565 This change does not affect users of the default configuration; it only affects
588 always enabled. It is consequently not possible anymore to disable at compile
593 disabling it can cause security issues and it is thus not recommended. If 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
623 PSA crypto API. If you have a use case that's not covered yet by this API,
636 surface, even if the code is supposedly not used.
662 and relied on that version in order to communicate with peers that are not up
691 This only affects TLS users who enabled `MBEDTLS_ZLIB_SUPPORT`. This will not
700 This does not affect people who used the default `mbedtls_config.h` and the default
701 list of ciphersuites, as RC4-based ciphersuites were already not negotiated in
730 This option has not had any effect for a long time. Please use the `lifetime`
777 For users which do not rely on raw keys and IV, adjusting to the new
820 This does not affect users who use the default `mbedtls_config.h`, as this option was
854 1. Mbed TLS 3.0 does not offer a migration path for the use case 1: Like many
865 This change does not affect users who used the default `mbedtls_config.h`, as the option
886 This change does not affect users who use the default `mbedtls_config.h`, as the
919 onwards, portable session cache implementations must not access fields of
994 is not useful since subsequent calls overwrite the effect of previous
1016 …rly only accepted for key exchanges but not for certificate signatures), SHA-224 (weaker hashes we…
1020 …on-5.1.1) deprecates it in TLS, and it is very rarely used, although it is not known to be weak at…
1032 This change does not affect users using default settings for 3DES in `mbedtls_config.h`