From: Tom Fay <tom@teamfay.co.uk>
Date: Thu, 12 Dec 2024 09:38:54 +0000 (+0000)
Subject: Correct documented KEM ids for OSSL_HPKE_str2suite
X-Git-Tag: openssl-3.4.1~38
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=79ce1e24c93cc6e329619feb3f1142627916ba3a;p=thirdparty%2Fopenssl.git

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)

(cherry picked from commit 62f9fd832ad8ddbeb6b835ef513e87c563256da2)
---

diff --git a/doc/man3/OSSL_HPKE_CTX_new.pod b/doc/man3/OSSL_HPKE_CTX_new.pod
index 6055ba6ea13..b282dc471a0 100644
--- a/doc/man3/OSSL_HPKE_CTX_new.pod
+++ b/doc/man3/OSSL_HPKE_CTX_new.pod
@@ -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".
 This can be used by command line tools that accept string form names for HPKE
 codepoints. Valid (case-insensitive) names are:
-"p256", "p384", "p521", "x25519" and "x448" for KEM,
-"hkdf-SHA256", "hkdf-SHA384" and "hkdf-SHA512" for KDF, and
-"aes-gcm-128", "aes-gcm-256" and "chacha20-poly1305" for AEAD.
+"p-256", "p-384", "p-521", "x25519" and "x448" for KEM,
+"hkdf-sha256", "hkdf-sha384" and "hkdf-sha512" for KDF, and
+"aes-gcm-128", "aes-gcm-256", "chacha20-poly1305" and "exporter" for AEAD.
 String variants of the numbers listed in L</OSSL_HPKE_SUITE Identifiers>
 can also be used.