openssl/providers/fips
Pauli 8948b57494 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)
2023-01-24 12:35:36 +00:00
..
build.info PROV: Relegate most of the FIPS provider code to libfips.a 2021-05-21 12:08:31 +02:00
fips_entry.c PROV: Relegate most of the FIPS provider code to libfips.a 2021-05-21 12:08:31 +02:00
fipsprov.c Put X25519 and X448 back as approved algorithms 2023-01-24 12:35:36 +00:00
self_test_data.inc Update FIPS KATs for 140-3 2022-11-02 08:42:46 +11:00
self_test_kats.c Update FIPS KATs for 140-3 2022-11-02 08:42:46 +11:00
self_test.c fips: verify that the RNG was restored after the self tests 2022-11-02 08:42:46 +11:00
self_test.h Rename OPENSSL_CTX prefix to OSSL_LIB_CTX 2020-10-15 11:59:53 +01:00