Automatically generated by Pod::Man 5.0102 (Pod::Simple 3.45)
Standard preamble:
========================================================================
..
.... \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>.
. ds C` "" . ds C' "" 'br\} . ds C` . ds C' 'br\}
Escape single quotes in literal strings from groff's Unicode transform.
If the F register is >0, we'll generate index entries on stderr for
titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
entries marked with X<> in POD. Of course, you'll have to process the
output yourself in some meaningful fashion.
Avoid warning from groff about undefined register 'F'.
.. .nr rF 0 . if \nF \{\ . de IX . tm Index:\\$1\t\\n%\t"\\$2" .. . if !\nF==2 \{\ . nr % 0 . nr F 2 . \} . \} .\} .rr rF ========================================================================
Title "EVP_PKEY-SLH-DSA 7ossl"
way too many mistakes in technical documents.
SLH-DSA (Stateless Hash-based Digital Signature Standard) uses small keys, but has relatively large signatures and is relatively slow performing all operations compared to ML-DSA. It does however have proven security proofs, since it relies only on hash functions.
Each of the different key types has an associated security parameter n. This value is one of 16, 24 or 32 for key types SLH-DSA*128*, SLH-DSA*192* and SLH-DSA*256*, respectively.
Both the public and private key components contain 2 elements of size n. Key generation generates the private key elements and one of the public key elements randomly, and the final public key element is computed from these values.
The public key has relatively small sizes of 32, 48 or 64 bytes, corresponding to the algorithm names of 128, 192 and 256 respectively.
The algorithms ending with s produce smaller signatures, but are much slower than the faster f variants.
The signature sizes for the s algorithm variants are 7856, 16224 and 29792 which correspond to the algorithm names of 128s, 192s and 256s respectively. The signature sizes for the f algorithm variants are 17088, 35664 and 49856 which correspond to the algorithm names containing 128f, 192f and 256f respectively.
Internally there are 7 hash related functions that are used for each algorithm. For algorithms containing SHAKE in their name SHAKE-256 is used for all functions. For the <SHA2-128> algorithms the functions use <MGF1-SHA-256>, <HMAC-SHA-256> and <SHA-256>. The remaining <SHA2> algorithms use <MGF1-SHA-512>, <HMAC-SHA-512>, <SHA-256> and <SHA-512>. See FIPS 205 Section 11.1 and 11.2 for more information.
Use EVP_PKEY_CTX_set_params() after calling EVP_PKEY_keygen_init().
The following parameters are gettable using EVP_PKEY_get_octet_string_param(), and settable when using EVP_PKEY_fromdata().
.Vb 2 EVP_PKEY_CTX *pctx = EVP_PKEY_CTX_new_from_name(NULL, "SLH-DSA-SHA2-128f", NULL); .Ve
An SLH-DSA key can be generated like this:
.Vb 1 pkey = EVP_PKEY_Q_keygen(NULL, NULL, "SLH-DSA-SHA2-128f"); .Ve
The key pair components can be extracted from a key by calling:
.Vb 2 uint8_t priv[64], pub[32]; size_t priv_len, pub_len; \& EVP_PKEY_get_octet_string_param(pkey, OSSL_PKEY_PARAM_PRIV_KEY, priv, sizeof(priv), &priv_len); EVP_PKEY_get_octet_string_param(pkey, OSSL_PKEY_PARAM_PUB_KEY, pub, sizeof(pub), &pub_len)); .Ve
Similar code can be used for the other key types such as "SLH-DSA-SHAKE-256f".
Licensed under the Apache License 2.0 (the "License"). You may not use this file except in compliance with the License. You can obtain a copy in the file LICENSE in the source distribution or at <https://www.openssl.org/source/license.html>.