-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update "use PSA" documentation (inc. strategy) #5757
Conversation
of RSA decryption would be still checking that is has the correct format: | ||
48 bytes, the first two matching the TLS version - note that this is timing | ||
sensitive.) | ||
|
||
HKDF: Expand not exposed on its own (TLS 1.3) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I updated the second paragraph of "PSA implementation in Mbed TLS" in the README but the third paragraph needs updating too (outdated link), and perhaps the first as well (do we still consider that PSA code is not as well reviewed as the rest?). @gilles-peskine-arm could you suggest a new version? Then I'd include it in this PR, to avoid the trouble of an extra PR with contextual conflicts. |
First paragraph: I think we can drop the maturity bit. We haven't done the systematic quality bar that I wanted to do, but we've rewritten pretty much all the original code and test coverage, so I think we've reached similar quality to the old code. Third paragraph: we've passed compliance with 1.0. We can just remove this paragraph. Although we might tweak the first paragraph to say that while we're a reference implementation, we don't aim to implement the whole thing, in particular we don't implement all the algorithms. |
Self-reminder: add ChangeLog entries too. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
That document was always temporary (said so at the top). Now superseded by https://github.com/orgs/Mbed-TLS/projects/1#column-18338322 Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
- misc updates about on-going/recent work - removal of the section about mixed-PSK: being done in Mbed-TLS#5762 - clarifications in some places - some typo fixes Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
The previous wording was wrong, there are parts that are affected. Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
It was initially motivated by the fact that the PSA Crypto APIs themselves were not stable. In the meantime, PSA Crypto has reached 1.0.0 so this no longer applies. If we want user to be able to fully benefit from PSA in order to isolate long-term secrets, they need to be able to use the new APIs with confidence. There is no reason to think those APIs are any more likely to change than any of our other APIs, and if they do, we'll follow the normal process (deprecated in favour of a new variant). For reference, the APIs in question are: mbedtls_pk_setup_opaque() // to use PSA-held ECDSA/RSA keys in TLS mbedtls_ssl_conf_psk_opaque() // for PSA-held PSKs in TLS mbedtls_ssl_set_hs_psk_opaque() // for PSA-held PSKs in TLS mbedtls_cipher_setup_psa() (deprecated in 3.2) mbedtls_pk_wrap_as_opaque() (documented internal, to be removed in 3.2) Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
The scope of the option has been expanded, now it makes more sense to describe it as "everything except ...". Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
Being resolved in Mbed-TLS#5784 Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
Also make a few general clarifications/improvements while at it. Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
Note: limitations of opaque PSKs changed from "TLS 1.2 only" to "none" since TLS 1.3 does not support PSK at all so far, and it is expected to support opaque PSKs as soon as it gains PSK support, it will be just a matter of selecting between psa_key_derivation_input_bytes() and psa_key_derivation_input_key() - and testing obviously. Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
There was a conflict in |
Description
Fixes #5621
Status
IN DEVELOPMENT - but what's there can already be reviewed. Will be finalized when we stabilize in preparation for 3.2.
Should be fully up to date as of 271c305 - just anticipates a bit on #5831 and #5844 being closed before the release.
Possible changes that may or may not happen before the release, and will require an update if they do:
psa-limitations.md
, EC-JPAKE 2: use in TLS (1.2) #5847 ->use-psa-crypto.md
psa-limitations.md
+use-psa-crypto.md
Requires Backporting
NO - 3.x only