Lines Matching refs:code

6 need to change their own code in order to make it work with Mbed TLS 3.0.
24 explain how to upgrade, and should be referred to when migrating code. Where a
31 Then browse `apidoc/deprecated.html` for guidance on upgrading deprecated code.
46 * In code, use `#include <mbedtls/build_info.h>`. Don't include `mbedtls/config.h` and don't refer …
48 …dtls/version.h`, this has moved to `include/mbedtls/build_info.h`. From C code, both headers now d…
70 …y, and these fields are not documented as public, you need to change your code. If an accessor (ge…
74 …r.MBEDTLS_PRIVATE(foo)`. Note that you do so at your own risk, since such code is likely to break …
150 and still relied on `compat-1.3.h` in their code.
152 Please use the new names directly in your code; `scripts/rename.pl` (from any
195 to call that from application code. However if you do (or if you want to
201 The option `MBEDTLS_ECP_FIXED_POINT_OPTIM` now increases code size and it does
204 If you are limited by code size, you can define `MBEDTLS_ECP_FIXED_POINT_OPTIM`
259 This was a trade-off between code size and countermeasures; it is no longer
260 relevant as the countermeasure is now always on at no cost in code size.
266 This makes no difference to a vast majority of applications. If your code takes a pointer to one of…
352 To migrate to the this change the user can keep the `*_ret` names in their code
354 renaming or to rename those functions in their code according to the list from
412 `mbedtls_cipher_finish()` in-between. If you code was missing that call,
473 This normally doesn't affect your code, unless you use pointers to reference
551 that case, please embed your own test certificates in your test code; now that
587 configuration options are removed and the X.509 code now behaves as if they were
635 and possibly downgrade attacks. More generally, more code means a larger attack
636 surface, even if the code is supposedly not used.
742 code maintenance.
773 returning an error code. It is the responsibility of the application
868 This option was a trade-off between functionality and code size: it allowed
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.
925 ### Changes in the SSL error code space