summaryrefslogtreecommitdiff
path: root/CHANGES.md
diff options
context:
space:
mode:
authorPauli <pauli@openssl.org>2023-01-20 09:32:49 +1100
committerHugo Landau <hlandau@openssl.org>2023-01-24 12:35:36 +0000
commit8948b5749410084ed1dfabf17a90df65efcf0f82 (patch)
tree6e03ead0d5bd7a1c819c0a3a9f47f0d35558d197 /CHANGES.md
parent8353b2dfacd723db5ba8b833b95e68e9600d1cf5 (diff)
downloadopenssl-new-8948b5749410084ed1dfabf17a90df65efcf0f82.tar.gz
Put X25519 and X448 back as approved algorithms
CMVP's answer when questioned about this being: X448 and X25519 uses Curve448 and Curve25519, respectfully, within an ECDH scheme. Therefore, it is possible for a key agreement scheme that uses Curve448 and Curve25519 to be used in the approved mode and be viewed as an allowed algorithm if requirements of Scenario X2 of IG D.8 and IG A.2 are met (or Scenario 3 of D.F and IG C.A for FIPS 140-3). The use of EdDSA in the approved mode is not permitted until FIPS 186-5 is published and part of CMVP guidance. Reviewed-by: Tomas Mraz <tomas@openssl.org> Reviewed-by: Hugo Landau <hlandau@openssl.org> (Merged from https://github.com/openssl/openssl/pull/20079)
Diffstat (limited to 'CHANGES.md')
0 files changed, 0 insertions, 0 deletions