1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
|
.\" -*- mode: troff; coding: utf-8 -*-
.\" Automatically generated by Pod::Man 5.0102 (Pod::Simple 3.45)
.\"
.\" Standard preamble:
.\" ========================================================================
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
..
.de Vb \" Begin verbatim text
.ft CW
.nf
.ne \\$1
..
.de Ve \" End verbatim text
.ft R
.fi
..
.\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>.
.ie n \{\
. ds C` ""
. ds C' ""
'br\}
.el\{\
. ds C`
. ds C'
'br\}
.\"
.\" Escape single quotes in literal strings from groff's Unicode transform.
.ie \n(.g .ds Aq \(aq
.el .ds Aq '
.\"
.\" 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'.
.de IX
..
.nr rF 0
.if \n(.g .if rF .nr rF 1
.if (\n(rF:(\n(.g==0)) \{\
. if \nF \{\
. de IX
. tm Index:\\$1\t\\n%\t"\\$2"
..
. if !\nF==2 \{\
. nr % 0
. nr F 2
. \}
. \}
.\}
.rr rF
.\" ========================================================================
.\"
.IX Title "EVP_PKEY-SLH-DSA 7ossl"
.TH EVP_PKEY-SLH-DSA 7ossl 2025-07-01 3.5.1 OpenSSL
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.nh
.SH NAME
EVP_PKEY\-SLH\-DSA, EVP_KEYMGMT\-SLH\-DSA,
EVP_PKEY\-SLH\-DSA\-SHA2\-128s, EVP_PKEY\-SLH\-DSA\-SHA2\-128f,
EVP_PKEY\-SLH\-DSA\-SHA2\-192s, EVP_PKEY\-SLH\-DSA\-SHA2\-192f,
EVP_PKEY\-SLH\-DSA\-SHA2\-256s, EVP_PKEY\-SLH\-DSA\-SHA2\-256f,
EVP_PKEY\-SLH\-DSA\-SHAKE\-128s, EVP_PKEY\-SLH\-DSA\-SHAKE\-128f,
EVP_PKEY\-SLH\-DSA\-SHAKE\-192s, EVP_PKEY\-SLH\-DSA\-SHAKE\-192f,
EVP_PKEY\-SLH\-DSA\-SHAKE\-256s, EVP_PKEY\-SLH\-DSA\-SHAKE\-256f
\&\- EVP_PKEY SLH\-DSA keytype and algorithm support
.SH DESCRIPTION
.IX Header "DESCRIPTION"
The \fBSLH\-DSA\-SHA2\-128s\fR, \fBEVP_PKEY\-SLH\-DSA\-SHA2\-128f\fR,
\&\fBSLH\-DSA\-SHA2\-192s\fR, \fBEVP_PKEY\-SLH\-DSA\-SHA2\-192f\fR,
\&\fBSLH\-DSA\-SHA2\-256s\fR, \fBEVP_PKEY\-SLH\-DSA\-SHA2\-256f\fR,
\&\fBSLH\-DSA\-SHAKE\-128s\fR, \fBEVP_PKEY\-SLH\-DSA\-SHAKE\-128f\fR,
\&\fBSLH\-DSA\-SHAKE\-192s\fR, \fBEVP_PKEY\-SLH\-DSA\-SHAKE\-192f\fR,
\&\fBSLH\-DSA\-SHAKE\-256s\fR and \fBEVP_PKEY\-SLH\-DSA\-SHAKE\-256f\fR key types are
implemented in OpenSSL's default and FIPS providers. These implementations
support the associated key, containing the public key \fIpub\fR and the
private key \fIpriv\fR.
.PP
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 \fBML-DSA\fR. It does however have proven security proofs,
since it relies only on hash functions.
.PP
Each of the different key types has an associated security parameter \fBn\fR.
This value is one of 16, 24 or 32 for key types \fBSLH\-DSA*128*\fR, \fBSLH\-DSA*192*\fR
and \fBSLH\-DSA*256*\fR, respectively.
.PP
Both the public and private key components contain 2 elements of size \fBn\fR.
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.
.PP
The public key has relatively small sizes of 32, 48 or 64 bytes,
corresponding to the algorithm names of 128, 192 and 256 respectively.
.PP
The algorithms ending with \fBs\fR produce smaller signatures, but are much slower
than the faster \fBf\fR variants.
.PP
The signature sizes for the \fBs\fR algorithm variants are 7856, 16224 and 29792
which correspond to the algorithm names of 128s, 192s and 256s respectively.
The signature sizes for the \fBf\fR algorithm variants are 17088, 35664 and 49856
which correspond to the algorithm names containing 128f, 192f and 256f respectively.
.PP
Internally there are 7 hash related functions that are used for each algorithm.
For algorithms containing \fBSHAKE\fR in their name \fBSHAKE\-256\fR 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.
.SS "Keygen Parameters"
.IX Subsection "Keygen Parameters"
.IP """seed"" (\fBOSSL_PKEY_PARAM_SLH_DSA_SEED\fR) <octet string>" 4
.IX Item """seed"" (OSSL_PKEY_PARAM_SLH_DSA_SEED) <octet string>"
Supplies values to use for the private seed, private prf and
public seed instead of generating random values. This is used for testing
purposes only. The length of the value supplied must be 3 * \fBn\fR.
.IP """properties"" (\fBOSSL_PKEY_PARAM_PROPERTIES\fR) <utf8_string>" 4
.IX Item """properties"" (OSSL_PKEY_PARAM_PROPERTIES) <utf8_string>"
Sets properties to be used when fetching algorithm implementations used for
SLH-DSA hashing operations.
.PP
Use \fBEVP_PKEY_CTX_set_params()\fR after calling \fBEVP_PKEY_keygen_init()\fR.
.SS "Common SLH-DSA parameters"
.IX Subsection "Common SLH-DSA parameters"
In addition to the common parameters that all keytypes should support (see
"Common Information Parameters" in \fBprovider\-keymgmt\fR\|(7)), the implementation of
these key types support the following.
.PP
The following parameters are gettable using \fBEVP_PKEY_get_octet_string_param()\fR,
and settable when using \fBEVP_PKEY_fromdata()\fR.
.IP """pub"" (\fBOSSL_PKEY_PARAM_PUB_KEY\fR) <octet string>" 4
.IX Item """pub"" (OSSL_PKEY_PARAM_PUB_KEY) <octet string>"
The public key has a size of 2 * \fBn\fR bytes.
i.e. It consists of the concatenation of PK.seed and PK.root
as defined by FIPS 205 Figure 16.
.IP """priv"" (\fBOSSL_PKEY_PARAM_PRIV_KEY\fR) <octet string>" 4
.IX Item """priv"" (OSSL_PKEY_PARAM_PRIV_KEY) <octet string>"
The private key has a size of 4 * \fBn\fR bytes, which includes the public key components.
i.e. It consists of the concatenation of SK.seed, SK.prf, PK.seed and PF.root
as defined by FIPS 205 Figure 15.
.IP """mandatory-digest"" (\fBOSSL_PKEY_PARAM_MANDATORY_DIGEST\fR) <UTF8 string>" 4
.IX Item """mandatory-digest"" (OSSL_PKEY_PARAM_MANDATORY_DIGEST) <UTF8 string>"
The empty string, signifying that no digest may be specified.
.SH "CONFORMING TO"
.IX Header "CONFORMING TO"
.IP "FIPS 205" 4
.IX Item "FIPS 205"
.SH EXAMPLES
.IX Header "EXAMPLES"
An \fBEVP_PKEY\fR context can be obtained by calling:
.PP
.Vb 2
\& EVP_PKEY_CTX *pctx =
\& EVP_PKEY_CTX_new_from_name(NULL, "SLH\-DSA\-SHA2\-128f", NULL);
.Ve
.PP
An \fBSLH-DSA\fR key can be generated like this:
.PP
.Vb 1
\& pkey = EVP_PKEY_Q_keygen(NULL, NULL, "SLH\-DSA\-SHA2\-128f");
.Ve
.PP
The key pair components can be extracted from a key by calling:
.PP
.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
.PP
Similar code can be used for the other key types such as "SLH\-DSA\-SHAKE\-256f".
.SH "SEE ALSO"
.IX Header "SEE ALSO"
\&\fBEVP_KEYMGMT\fR\|(3), \fBEVP_PKEY\fR\|(3), \fBprovider\-keymgmt\fR\|(7),
\&\fBEVP_SIGNATURE\-SLH\-DSA\fR\|(7)
.SH HISTORY
.IX Header "HISTORY"
This functionality was added in OpenSSL 3.5.
.SH COPYRIGHT
.IX Header "COPYRIGHT"
Copyright 2024\-2025 The OpenSSL Project Authors. All Rights Reserved.
.PP
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>.
|
