Lines Matching refs:need
6 need to change their own code in order to make it work with Mbed TLS 3.0.
70 …cture fields directly, and these fields are not documented as public, you need to change your code…
82 If you were relying on these functions, you'll now need to change to using your
194 - The functions `mbedtls_xxx_process()` were removed. You normally don't need
216 you will need to add `#define MBEDTLS_SHA224_C` option to your config.
229 `MBEDTLS_SHA512_NO_SHA384` and you need the SHA-384 algorithm, then add
266 …ications. If your code takes a pointer to one of these functions, you may need to change the type …
370 you were using the PKCS#1 v2.1 encoding you now need, subsequently to the call
474 those functions. In this case, you'll need to update the type of your pointers
488 You now need to pass a properly seeded, cryptographically secure RNG to all
490 pass `NULL` as the context pointer `p_rng` if your RNG function doesn't need a
503 You now need to pass a properly seeded, cryptographically secure RNG when
524 If you're providing alt implementations of ECP or RSA, you'll need to add our
531 and explain your need; we'll consider adding a new API in a future version.
609 If you are working with the pre-V3 certificates you need to switch to the
869 users who didn't need that feature to avoid paying the cost in code size, by
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/
903 Those users will need to modify the API of their session cache
1022 If you still need to accept certificates signed with algorithms that have been removed from the def…
1028 If you still need to allow hashes and curves in TLS that have been removed from the default configu…