-
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
Mixed PSK 2b: support DHE-PSK #5664
Comments
Got a question regarding this one. The PSA Mixed-PSK master key derivation is handled here (in this version only RSA-PSK is handled): Lines 5150 to 5199 in 36dc5b3
The other secret needed for master key derivation is kept in
But for DHE seems that premaster is not filled in this part of code: I focused here on client side only. |
The PSA crypto layer doesn't support DH yet. USE_PSA_CRYPTO code can't support DHE until that's done. I haven't followed when we've scheduled to do that — probably later, because non-EC DH isn't used much anymore. |
Yes, sorry, I should have mentioned that bit of context in the task's description. For DHE-PSK, the DHE part will still be done by the legacy API, and only the derivation "DHE output + PSK -> MS" will be done by PSA. (More generally, for all the xxx-PSK tasks, no change is intended in the xxx part: either it has already been done in previous EPICs, or to be done later.) The DHE part of the DHE-PSK key exchange goes as follows client-side:
The thing is, |
This task is to add support for DHE-PSK using PSA-held (aka opaque) keys, that is, keys provisioned with
mbedtls_ssl_conf_psk_opaque()
ormbedtls_ssl_set_hs_psk_opaque()
(used in the PSK callback).The task is done when there are passing tests in
ssl-opt.sh
using DHE-PSK withpsk_opaque=1
with sufficient coverage (client and/or server, static conf and/or callback, see existing tests for pure PSK).Depends on: #5662 (also provides context and references).
Related: #5663, #5665
The text was updated successfully, but these errors were encountered: