From 5c8c9e068e16b704f8fd9e2eb3a9f97046733401 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Manuel=20P=C3=A9gouri=C3=A9-Gonnard?= Date: Wed, 29 Mar 2023 10:33:03 +0200 Subject: [PATCH] Minor improvements MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Manuel Pégourié-Gonnard --- docs/architecture/psa-migration/psa-limitations.md | 2 +- docs/use-psa-crypto.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/architecture/psa-migration/psa-limitations.md b/docs/architecture/psa-migration/psa-limitations.md index b81aeb47a..29d7c5330 100644 --- a/docs/architecture/psa-migration/psa-limitations.md +++ b/docs/architecture/psa-migration/psa-limitations.md @@ -15,7 +15,7 @@ Restartable (aka interruptible) ECC operations ---------------------------------------------- Support for interruptible ECDSA sign/verify was added to PSA in Mbed TLS 3.4. -However support for interruptible ECDH is not present yet. Also, PK, X.509 and +However, support for interruptible ECDH is not present yet. Also, PK, X.509 and TLS have not yet been adapted to take advantage of the new PSA APIs. See: - ; - ; diff --git a/docs/use-psa-crypto.md b/docs/use-psa-crypto.md index 305dd736b..7c0397f62 100644 --- a/docs/use-psa-crypto.md +++ b/docs/use-psa-crypto.md @@ -29,7 +29,7 @@ that's the case for hashes. `psa_crypto_init()` before you call any other `psa_xxx()` function. Other modules in the library (non-PSA crypto APIs, X.509, TLS) may or may not use PSA Crypto but you're not required to call `psa_crypto_init()` before calling -non-PSA functions, unless when explicitly documented (TLS 1.3). +non-PSA functions, unless explicitly documented (TLS 1.3). - `MBEDTLS_USE_PSA_CRYPTO` means that X.509 and TLS will use PSA Crypto as much as possible (that is, everywhere except for features that are not supported by PSA Crypto, see "Internal Changes" below for a complete list of