Lines Matching full:mbed

1 # Migrating from Mbed TLS 2.x to Mbed TLS 3.0
3 This guide details the steps required to migrate from Mbed TLS version 2.x to
4 Mbed TLS version 3.0 or greater. Unlike normal releases, Mbed TLS 3.0 breaks
6 need to change their own code in order to make it work with Mbed TLS 3.0.
18 Much of the information needed to determine a migration path can be found in the Mbed TLS 2.x docum…
21 ## Accessing the Mbed TLS 2.x documentation
23 For features previously marked as deprecated, Mbed TLS 2.x documentation may
28 It's best to use the latest version of Mbed TLS 2.x for this purpose, which is the 2.28 LTS release.
30 the instructions in the [Documentation section of the README](https://github.com/Mbed-TLS/mbedtls/b…
34 suffixed with `_ret`. In Mbed TLS 3.x, this change may not be required, as most
56 Defining it to a particular value will ensure that Mbed TLS interprets
58 used by the Mbed TLS release whose `MBEDTLS_VERSION_NUMBER` has the same
60 The only value supported by Mbed TLS 3.0.0 is `0x03000000`.
64 …es (`struct` types) declared in public headers is no longer supported. In Mbed TLS 3, the layout o…
66 …re some fields are guaranteed to remain stable throughout the lifetime of Mbed TLS 3.x. These fiel…
72 …equest against Mbed TLS](https://github.com/Mbed-TLS/mbedtls/issues/new?template=feature_request.m…
74 …u do so at your own risk, since such code is likely to break in a future minor version of Mbed TLS.
144 <https://mbed-tls.readthedocs.io/en/latest/kb/how-to/add-entropy-sources-to-entropy-pool> for more
147 ### Remove helpers for the transition from Mbed TLS 1.3 to Mbed TLS 2.0
149 This only affects people who've been using Mbed TLS since before version 2.0
239 * `mbedtls_gcm_update()` now takes an extra parameter to indicate the actual output length. In Mbed…
569 they don't recognize, and this is what Mbed TLS does by default. This option
605 containing extensions were never compliant. Mbed TLS now rejects them with a
786 Mbed TLS team on the mailing list, to let the team know about their
806 In Mbed TLS 2.x, users would observe later calls overwriting
808 the one that has been configured last. In Mbed TLS 3.0,
812 To achieve equivalent functionality when migrating to Mbed TLS 3.0,
854 1. Mbed TLS 3.0 does not offer a migration path for the use case 1: Like many
855    other Mbed TLS structures, the structure of `mbedtls_ssl_session` is no
856    longer part of the public API in Mbed TLS 3.0, and direct structure field
901 from the one Mbed TLS implements in `library/ssl_cache.c`.
923 on the Mbed TLS mailing list.
993 - Calling `mbedtls_ssl_set_session()` multiple times in Mbed TLS 2.x