General update of PSA strategy documentation
Not related to the changes in this PR, except in the next commit I'll
update the strategy document for changes in this PR and to outline
likely follow-ups, and while looking at the document I noticed a few
things that needed updated, so here there are in their own commit.
Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
diff --git a/docs/use-psa-crypto.md b/docs/use-psa-crypto.md
index c849221..b22d37f 100644
--- a/docs/use-psa-crypto.md
+++ b/docs/use-psa-crypto.md
@@ -18,7 +18,7 @@
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;
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
+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
@@ -100,7 +100,7 @@
- verification of RSA-PSS signatures with a salt length that is different from
the hash length.
-Other than the above exceptions, all crypto operations are based on PSA when
+Other than the above exception, all crypto operations are based on PSA when
`MBEDTLS_USE_PSA_CRYPTO` is enabled.
### PK layer: most crypto operations based on PSA
@@ -108,8 +108,8 @@
Current exception:
- verification of RSA-PSS signatures with a salt length that is different from
- the hash length.
+ the hash length, or with an MGF hash that's different from the message hash.
-Other than the above exceptions, all crypto operations are based on PSA when
+Other than the above exception, all crypto operations are based on PSA when
`MBEDTLS_USE_PSA_CRYPTO` is enabled.