Backward compatibility: the key store with drivers

Promise that we will try to keep backward compatibility with basic driver
usage, but not with more experimental aspects.

Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
This commit is contained in:
Gilles Peskine 2022-06-20 18:50:09 +02:00
parent 9956efaf32
commit 4b873874a3
2 changed files with 9 additions and 2 deletions

View file

@ -78,6 +78,12 @@ Mbed TLS 3.x can also read keys written by Mbed TLS 2.25.0 through 2.28.x
LTS, but future major version upgrades (for example from 2.28.x/3.x to 4.y) LTS, but future major version upgrades (for example from 2.28.x/3.x to 4.y)
may require the use of an upgrade tool. may require the use of an upgrade tool.
Note that this guarantee does not currently fully extend to drivers, which
are an experimental feature. We intend to maintain compatibility with the
basic use of drivers from Mbed TLS 2.28.0 onwards, even if driver APIs
change. However, for more experimental parts of the driver interface, such
as the use of driver state, we do not yet guarantee backward compatibility.
## Long-time support branches ## Long-time support branches
For the LTS branches, additionally we try very hard to also maintain ABI For the LTS branches, additionally we try very hard to also maintain ABI

View file

@ -1184,8 +1184,9 @@
* *
* Requires: MBEDTLS_PSA_CRYPTO_C * Requires: MBEDTLS_PSA_CRYPTO_C
* *
* \warning This interface is experimental and may change or be removed * \warning This interface is experimental. We intend to maintain backward
* without notice. * compatibility with application code that relies on drivers,
* but the driver interfaces may change without notice.
*/ */
//#define MBEDTLS_PSA_CRYPTO_DRIVERS //#define MBEDTLS_PSA_CRYPTO_DRIVERS