From 0dba51cfad6b975e64e8237e85e87ed01d84c0a4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Manuel=20P=C3=A9gouri=C3=A9-Gonnard?= Date: Tue, 7 Jun 2022 10:28:02 +0200 Subject: [PATCH] Fix list of what's common to TLS 1.2 and 1.3 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Manuel Pégourié-Gonnard --- docs/use-psa-crypto.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/use-psa-crypto.md b/docs/use-psa-crypto.md index c01265896f..8261b8b93c 100644 --- a/docs/use-psa-crypto.md +++ b/docs/use-psa-crypto.md @@ -16,9 +16,10 @@ module. Scope: `MBEDTLS_USE_PSA_CRYPTO` has no effect on the parts of the code that are specific to TLS 1.3; those parts always use PSA Crypto. The parts of the -TLS 1.3 code that are common with TLS 1.2, however, follow this option (this -is currently just the record protection code, and X.509). You need to enable -`MBEDTLS_USE_PSA_CRYPTO` if you want TLS 1.3 to use PSA everywhere. +TLS 1.3 code that are common with TLS 1.2, however, follow this option; +currently this is the record protection code, computation of the running +handshake hash, and X.509). You need to enable `MBEDTLS_USE_PSA_CRYPTO` if you +want TLS 1.3 to use PSA everywhere. New APIs / API extensions -------------------------