Correct documented KEM ids for OSSL_HPKE_str2suite

CLA: trivial

Reviewed-by: Hugo Landau <hlandau@devever.net>
Reviewed-by: Tomas Mraz <tomas@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/26159)
This commit is contained in:
Tom Fay 2024-12-12 09:38:54 +00:00 committed by Tomas Mraz
parent d8af77e736
commit 62f9fd832a
1 changed files with 3 additions and 3 deletions

View File

@ -454,9 +454,9 @@ The input I<str> should be a comma-separated string with a KEM,
KDF and AEAD name in that order, for example "x25519,hkdf-sha256,aes128gcm". KDF and AEAD name in that order, for example "x25519,hkdf-sha256,aes128gcm".
This can be used by command line tools that accept string form names for HPKE This can be used by command line tools that accept string form names for HPKE
codepoints. Valid (case-insensitive) names are: codepoints. Valid (case-insensitive) names are:
"p256", "p384", "p521", "x25519" and "x448" for KEM, "p-256", "p-384", "p-521", "x25519" and "x448" for KEM,
"hkdf-SHA256", "hkdf-SHA384" and "hkdf-SHA512" for KDF, and "hkdf-sha256", "hkdf-sha384" and "hkdf-sha512" for KDF, and
"aes-gcm-128", "aes-gcm-256" and "chacha20-poly1305" for AEAD. "aes-gcm-128", "aes-gcm-256", "chacha20-poly1305" and "exporter" for AEAD.
String variants of the numbers listed in L</OSSL_HPKE_SUITE Identifiers> String variants of the numbers listed in L</OSSL_HPKE_SUITE Identifiers>
can also be used. can also be used.