Lines Matching refs:version
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
28 It's best to use the latest version of Mbed TLS 2.x for this purpose, which is the 2.28 LTS release.
48 * If you had a tool that parsed the library version from `include/mbedtls/version.h`, this has move…
55 A config file version symbol, `MBEDTLS_CONFIG_VERSION` was introduced.
74 …u do so at your own risk, since such code is likely to break in a future minor version of Mbed TLS.
149 This only affects people who've been using Mbed TLS since before version 2.0
196 provide your own version of that function), please use
217 Current version of the library does not support enabling `MBEDTLS_SHA256_C`
513 API were removed from version 1.0 of specification. Please switch to the new
531 and explain your need; we'll consider adding a new API in a future version.
642 version. There is no migration path since the feature is no longer relevant.
644 As a consequence of currently supporting only one version of (D)TLS (and in the
645 future 1.3 which will have a different version negotiation mechanism), support
649 As a consequence of currently supporting only one version of (D)TLS (and in the
651 configuring ciphersuites separately for each version via
662 and relied on that version in order to communicate with peers that are not up
680 regardless of whether the standard version was used or compatibility version