Debian Codegraph @

upstream/debian-trixie/man3/SSL_CONF_cmd.3ssl

raw
1 .\" -*- mode: troff; coding: utf-8 -*-
2 .\" Automatically generated by Pod::Man 5.0102 (Pod::Simple 3.45)
3 .\"
4 .\" Standard preamble:
5 .\" ========================================================================
6 .de Sp \" Vertical space (when we can't use .PP)
7 .if t .sp .5v
8 .if n .sp
9 ..
10 .de Vb \" Begin verbatim text
11 .ft CW
12 .nf
13 .ne \\$1
14 ..
15 .de Ve \" End verbatim text
16 .ft R
17 .fi
18 ..
19 .\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>.
20 .ie n \{\
21 . ds C` ""
22 . ds C' ""
23 'br\}
24 .el\{\
25 . ds C`
26 . ds C'
27 'br\}
28 .\"
29 .\" Escape single quotes in literal strings from groff's Unicode transform.
30 .ie \n(.g .ds Aq \(aq
31 .el .ds Aq '
32 .\"
33 .\" If the F register is >0, we'll generate index entries on stderr for
34 .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
35 .\" entries marked with X<> in POD. Of course, you'll have to process the
36 .\" output yourself in some meaningful fashion.
37 .\"
38 .\" Avoid warning from groff about undefined register 'F'.
39 .de IX
40 ..
41 .nr rF 0
42 .if \n(.g .if rF .nr rF 1
43 .if (\n(rF:(\n(.g==0)) \{\
44 . if \nF \{\
45 . de IX
46 . tm Index:\\$1\t\\n%\t"\\$2"
47 ..
48 . if !\nF==2 \{\
49 . nr % 0
50 . nr F 2
51 . \}
52 . \}
53 .\}
54 .rr rF
55 .\" ========================================================================
56 .\"
57 .IX Title "SSL_CONF_CMD 3SSL"
58 .TH SSL_CONF_CMD 3SSL 2026-04-07 3.5.6 OpenSSL
59 .\" For nroff, turn off justification. Always turn off hyphenation; it makes
60 .\" way too many mistakes in technical documents.
61 .if n .ad l
62 .nh
63 .SH NAME
64 SSL_CONF_cmd_value_type,
65 SSL_CONF_cmd \- send configuration command
66 .SH SYNOPSIS
67 .IX Header "SYNOPSIS"
68 .Vb 1
69 \& #include <openssl/ssl.h>
70 \&
71 \& int SSL_CONF_cmd(SSL_CONF_CTX *ctx, const char *option, const char *value);
72 \& int SSL_CONF_cmd_value_type(SSL_CONF_CTX *ctx, const char *option);
73 .Ve
74 .SH DESCRIPTION
75 .IX Header "DESCRIPTION"
76 The function \fBSSL_CONF_cmd()\fR performs configuration operation \fBoption\fR with
77 optional parameter \fBvalue\fR on \fBctx\fR. Its purpose is to simplify application
78 configuration of \fBSSL_CTX\fR or \fBSSL\fR structures by providing a common
79 framework for command line options or configuration files.
80 .PP
81 \&\fBSSL_CONF_cmd_value_type()\fR returns the type of value that \fBoption\fR refers to.
82 .SH "SUPPORTED COMMAND LINE COMMANDS"
83 .IX Header "SUPPORTED COMMAND LINE COMMANDS"
84 Currently supported \fBoption\fR names for command lines (i.e. when the
85 flag \fBSSL_CONF_FLAG_CMDLINE\fR is set) are listed below. Note: all \fBoption\fR
86 names are case sensitive. Unless otherwise stated commands can be used by
87 both clients and servers and the \fBvalue\fR parameter is not used. The default
88 prefix for command line commands is \fB\-\fR and that is reflected below.
89 .IP \fB\-bugs\fR 4
90 .IX Item "-bugs"
91 Various bug workarounds are set, same as setting \fBSSL_OP_ALL\fR.
92 .IP \fB\-no_comp\fR 4
93 .IX Item "-no_comp"
94 Disables support for SSL/TLS compression, same as setting
95 \&\fBSSL_OP_NO_COMPRESSION\fR.
96 As of OpenSSL 1.1.0, compression is off by default.
97 .IP \fB\-comp\fR 4
98 .IX Item "-comp"
99 Enables support for SSL/TLS compression, same as clearing
100 \&\fBSSL_OP_NO_COMPRESSION\fR.
101 This command was introduced in OpenSSL 1.1.0.
102 As of OpenSSL 1.1.0, compression is off by default. TLS compression can only be
103 used in security level 1 or lower. From OpenSSL 3.2.0 and above the default
104 security level is 2, so this option will have no effect without also changing
105 the security level. See \fBSSL_CTX_set_security_level\fR\|(3).
106 .IP \fB\-no_ticket\fR 4
107 .IX Item "-no_ticket"
108 Disables support for session tickets, same as setting \fBSSL_OP_NO_TICKET\fR.
109 .IP \fB\-serverpref\fR 4
110 .IX Item "-serverpref"
111 Use server and not client preference order when determining which cipher suite,
112 signature algorithm or elliptic curve to use for an incoming connection.
113 Equivalent to \fBSSL_OP_CIPHER_SERVER_PREFERENCE\fR. Only used by servers.
114 .IP \fB\-client_renegotiation\fR 4
115 .IX Item "-client_renegotiation"
116 Allows servers to accept client-initiated renegotiation. Equivalent to
117 setting \fBSSL_OP_ALLOW_CLIENT_RENEGOTIATION\fR.
118 Only used by servers.
119 .IP \fB\-legacy_renegotiation\fR 4
120 .IX Item "-legacy_renegotiation"
121 Permits the use of unsafe legacy renegotiation. Equivalent to setting
122 \&\fBSSL_OP_ALLOW_UNSAFE_LEGACY_RENEGOTIATION\fR.
123 .IP \fB\-no_renegotiation\fR 4
124 .IX Item "-no_renegotiation"
125 Disables all attempts at renegotiation in (D)TLSv1.2 and earlier, same as setting
126 \&\fBSSL_OP_NO_RENEGOTIATION\fR.
127 .IP \fB\-no_resumption_on_reneg\fR 4
128 .IX Item "-no_resumption_on_reneg"
129 Sets \fBSSL_OP_NO_SESSION_RESUMPTION_ON_RENEGOTIATION\fR. Only used by servers.
130 .IP "\fB\-legacy_server_connect\fR, \fB\-no_legacy_server_connect\fR" 4
131 .IX Item "-legacy_server_connect, -no_legacy_server_connect"
132 Permits or prohibits the use of unsafe legacy renegotiation for OpenSSL
133 clients only. Equivalent to setting or clearing \fBSSL_OP_LEGACY_SERVER_CONNECT\fR.
134 .IP \fB\-prioritize_chacha\fR 4
135 .IX Item "-prioritize_chacha"
136 Prioritize ChaCha ciphers when the client has a ChaCha20 cipher at the top of
137 its preference list. This usually indicates a client without AES hardware
138 acceleration (e.g. mobile) is in use. Equivalent to \fBSSL_OP_PRIORITIZE_CHACHA\fR.
139 Only used by servers. Requires \fB\-serverpref\fR.
140 .IP \fB\-allow_no_dhe_kex\fR 4
141 .IX Item "-allow_no_dhe_kex"
142 In TLSv1.3 allow a non\-(ec)dhe based key exchange mode on resumption. This means
143 that there will be no forward secrecy for the resumed session.
144 .IP \fB\-prefer_no_dhe_kex\fR 4
145 .IX Item "-prefer_no_dhe_kex"
146 In TLSv1.3, on resumption let the server prefer a non\-(ec)dhe based key
147 exchange mode over an (ec)dhe based one. Requires \fB\-allow_no_dhe_kex\fR.
148 Equivalent to \fBSSL_OP_PREFER_NO_DHE_KEX\fR. Only used by servers.
149 .IP \fB\-strict\fR 4
150 .IX Item "-strict"
151 Enables strict mode protocol handling. Equivalent to setting
152 \&\fBSSL_CERT_FLAG_TLS_STRICT\fR.
153 .IP "\fB\-sigalgs\fR \fIalgs\fR" 4
154 .IX Item "-sigalgs algs"
155 This sets the supported signature algorithms for TLSv1.2 and TLSv1.3.
156 For clients this value is used directly for the supported signature
157 algorithms extension. For servers it is used to determine which signature
158 algorithms to support.
159 .Sp
160 The \fBalgs\fR argument should be a colon separated list of signature
161 algorithms in order of decreasing preference of the form \fBalgorithm+hash\fR
162 or \fBsignature_scheme\fR. For the default providers shipped with OpenSSL,
163 \&\fBalgorithm\fR is one of \fBRSA\fR, \fBDSA\fR or \fBECDSA\fR and
164 \&\fBhash\fR is a supported algorithm OID short name such as \fBSHA1\fR, \fBSHA224\fR,
165 \&\fBSHA256\fR, \fBSHA384\fR or \fBSHA512\fR.
166 \&\fBsignature_scheme\fR is one of the signature schemes defined
167 in TLSv1.3, specified using the IETF name, e.g., \fBecdsa_secp256r1_sha256\fR,
168 \&\fBed25519\fR, or \fBrsa_pss_pss_sha256\fR. Additional providers may make available
169 further algorithms via the TLS-SIGALG capability.
170 Signature scheme names and public key algorithm names (but not the hash names)
171 in the \fBalgorithm+hash\fR form are case-insensitive.
172 See \fBprovider\-base\fR\|(7).
173 .Sp
174 If this option is not set then all signature algorithms supported by all
175 activated providers are permissible.
176 .Sp
177 Note: algorithms which specify a PKCS#1 v1.5 signature scheme (either by
178 using \fBRSA\fR as the \fBalgorithm\fR or by using one of the \fBrsa_pkcs1_*\fR
179 identifiers) are ignored in TLSv1.3 and will not be negotiated.
180 .IP "\fB\-client_sigalgs\fR \fIalgs\fR" 4
181 .IX Item "-client_sigalgs algs"
182 This sets the supported signature algorithms associated with client
183 authentication for TLSv1.2 and TLSv1.3. For servers the \fBalgs\fR is used
184 in the \fBsignature_algorithms\fR field of a \fBCertificateRequest\fR message.
185 For clients it is used to determine which signature algorithm to use with
186 the client certificate. If a server does not request a certificate this
187 option has no effect.
188 .Sp
189 The syntax of \fBalgs\fR is identical to \fB\-sigalgs\fR. If not set, then the
190 value set for \fB\-sigalgs\fR will be used instead.
191 .IP "\fB\-groups\fR \fIgroups\fR" 4
192 .IX Item "-groups groups"
193 This sets the supported groups. For clients, the groups are sent using
194 the supported groups extension. For servers, it is used to determine which
195 group to use. This setting affects groups used for signatures (in TLSv1.2
196 and earlier) and key exchange.
197 .Sp
198 In its simplest form the \fIgroups\fR argument is a colon separated list of
199 groups. The preferred names are those listed in the IANA
200 TLS Supported Groups <https://www.iana.org/assignments/tls-parameters/tls-parameters.xhtml#tls-parameters-8>
201 registry.
202 .Sp
203 For some groups, OpenSSL supports additional aliases.
204 Such an alias could be a \fBNIST\fR name (e.g. \fBP\-256\fR), an OpenSSL OID name
205 (e.g. \fBprime256v1\fR), or some other commonly used name.
206 Group names are case-insensitive in OpenSSL 3.5 and later.
207 The list should be in order of preference with the most preferred group first.
208 .Sp
209 The first group listed will also be used for the \fBkey_share\fR sent by a client
210 in a TLSv1.3 \fBClientHello\fR.
211 .Sp
212 The commands below list the IANA names for TLS 1.2 and TLS 1.3,
213 respectively:
214 .Sp
215 .Vb 2
216 \& $ openssl list \-tls1_2 \-tls\-groups
217 \& $ openssl list \-tls1_3 \-tls\-groups
218 .Ve
219 .Sp
220 The recommended groups for TLS 1.3 are presently documented in the default
221 TLS group list in the OpenSSL code base. Starting with OpenSSL 3.5, the
222 hybrid algorithm \fBX25519MLKEM768\fR is first in this default list.
223 It mitigates against threats from future quantum computers while
224 still providing state-of-the-art classical key exchange protection.
225 .Sp
226 Further details regarding post-quantum algorithm considerations are documented
227 in the HISTORY section below.
228 .Sp
229 An enriched alternative syntax, that enables clients to send multiple keyshares
230 and allows servers to prioritise some groups over others, is described in
231 \&\fBSSL_CTX_set1_groups_list\fR\|(3).
232 Since TLS 1.2 has neither keyshares nor a hello retry mechanism, with TLS 1.2
233 the enriched syntax is ultimately equivalent to just a simple ordered list of
234 groups, as with the simple form above.
235 .IP "\fB\-curves\fR \fIgroups\fR" 4
236 .IX Item "-curves groups"
237 This is a synonym for the \fB\-groups\fR command.
238 .IP "\fB\-named_curve\fR \fIcurve\fR" 4
239 .IX Item "-named_curve curve"
240 This sets the temporary curve used for ephemeral ECDH modes.
241 This is only applicable in TLS 1.0 and 1.1, and should not be used with later
242 protocol versions.
243 .Sp
244 The \fIcurve\fR argument is a curve name or the special value \fBauto\fR which
245 picks an appropriate curve based on client and server preferences. The
246 curve can be either the \fBNIST\fR name (e.g. \fBP\-256\fR) or an OpenSSL OID name
247 (e.g. \fBprime256v1\fR).
248 Even with TLS 1.0 and 1.1, the default value of \f(CW\*(C`auto\*(C'\fR is strongly recommended
249 over choosing a specific curve.
250 Curve names are case-insensitive in OpenSSL 3.5 and later.
251 .IP \fB\-tx_cert_comp\fR 4
252 .IX Item "-tx_cert_comp"
253 Enables support for sending TLSv1.3 compressed certificates.
254 .IP \fB\-no_tx_cert_comp\fR 4
255 .IX Item "-no_tx_cert_comp"
256 Disables support for sending TLSv1.3 compressed certificates.
257 .IP \fB\-rx_cert_comp\fR 4
258 .IX Item "-rx_cert_comp"
259 Enables support for receiving TLSv1.3 compressed certificates.
260 .IP \fB\-no_rx_cert_comp\fR 4
261 .IX Item "-no_rx_cert_comp"
262 Disables support for receiving TLSv1.3 compressed certificates.
263 .IP \fB\-comp\fR 4
264 .IX Item "-comp"
265 .PD 0
266 .IP "\fB\-cipher\fR \fIciphers\fR" 4
267 .IX Item "-cipher ciphers"
268 .PD
269 Sets the TLSv1.2 and below ciphersuite list to \fBciphers\fR. This list will be
270 combined with any configured TLSv1.3 ciphersuites. Note: syntax checking
271 of \fBciphers\fR is currently not performed unless a \fBSSL\fR or \fBSSL_CTX\fR
272 structure is associated with \fBctx\fR.
273 .IP "\fB\-ciphersuites\fR \fI1.3ciphers\fR" 4
274 .IX Item "-ciphersuites 1.3ciphers"
275 Sets the available ciphersuites for TLSv1.3 to value. This is a
276 colon-separated list of TLSv1.3 ciphersuite names in order of preference. This
277 list will be combined any configured TLSv1.2 and below ciphersuites.
278 See \fBopenssl\-ciphers\fR\|(1) for more information.
279 .IP "\fB\-min_protocol\fR \fIminprot\fR, \fB\-max_protocol\fR \fImaxprot\fR" 4
280 .IX Item "-min_protocol minprot, -max_protocol maxprot"
281 Sets the minimum and maximum supported protocol.
282 Currently supported protocol values are \fBSSLv3\fR, \fBTLSv1\fR, \fBTLSv1.1\fR,
283 \&\fBTLSv1.2\fR, \fBTLSv1.3\fR for TLS; \fBDTLSv1\fR, \fBDTLSv1.2\fR for DTLS, and \fBNone\fR
284 for no limit.
285 If either the lower or upper bound is not specified then only the other bound
286 applies, if specified.
287 If your application supports both TLS and DTLS you can specify any of these
288 options twice, once with a bound for TLS and again with an appropriate bound
289 for DTLS.
290 To restrict the supported protocol versions use these commands rather than the
291 deprecated alternative commands below.
292 .IP "\fB\-record_padding\fR \fIpadding\fR" 4
293 .IX Item "-record_padding padding"
294 Controls use of TLSv1.3 record layer padding. \fBpadding\fR is a string of the
295 form "number[,number]" where the (required) first number is the padding block
296 size (in octets) for application data, and the optional second number is the
297 padding block size for handshake and alert messages. If the optional second
298 number is omitted, the same padding will be applied to all messages.
299 .Sp
300 Padding attempts to pad TLSv1.3 records so that they are a multiple of the set
301 length on send. A value of 0 or 1 turns off padding as relevant. Otherwise, the
302 values must be >1 or <=16384.
303 .IP \fB\-debug_broken_protocol\fR 4
304 .IX Item "-debug_broken_protocol"
305 Ignored.
306 .IP \fB\-no_middlebox\fR 4
307 .IX Item "-no_middlebox"
308 Turn off "middlebox compatibility", as described below.
309 .SS "Additional Options"
310 .IX Subsection "Additional Options"
311 The following options are accepted by \fBSSL_CONF_cmd()\fR, but are not
312 processed by the OpenSSL commands.
313 .IP "\fB\-cert\fR \fIfile\fR" 4
314 .IX Item "-cert file"
315 Attempts to use \fBfile\fR as the certificate for the appropriate context. It
316 currently uses \fBSSL_CTX_use_certificate_chain_file()\fR if an \fBSSL_CTX\fR
317 structure is set or \fBSSL_use_certificate_file()\fR with filetype PEM if an
318 \&\fBSSL\fR structure is set. This option is only supported if certificate
319 operations are permitted.
320 .IP "\fB\-key\fR \fIfile\fR" 4
321 .IX Item "-key file"
322 Attempts to use \fBfile\fR as the private key for the appropriate context. This
323 option is only supported if certificate operations are permitted. Note:
324 if no \fB\-key\fR option is set then a private key is not loaded unless the
325 flag \fBSSL_CONF_FLAG_REQUIRE_PRIVATE\fR is set.
326 .IP "\fB\-dhparam\fR \fIfile\fR" 4
327 .IX Item "-dhparam file"
328 Attempts to use \fBfile\fR as the set of temporary DH parameters for
329 the appropriate context. This option is only supported if certificate
330 operations are permitted.
331 .IP "\fB\-no_ssl3\fR, \fB\-no_tls1\fR, \fB\-no_tls1_1\fR, \fB\-no_tls1_2\fR, \fB\-no_tls1_3\fR" 4
332 .IX Item "-no_ssl3, -no_tls1, -no_tls1_1, -no_tls1_2, -no_tls1_3"
333 Disables protocol support for SSLv3, TLSv1.0, TLSv1.1, TLSv1.2 or TLSv1.3 by
334 setting the corresponding options \fBSSL_OP_NO_SSLv3\fR, \fBSSL_OP_NO_TLSv1\fR,
335 \&\fBSSL_OP_NO_TLSv1_1\fR, \fBSSL_OP_NO_TLSv1_2\fR and \fBSSL_OP_NO_TLSv1_3\fR
336 respectively. These options are deprecated, use \fB\-min_protocol\fR and
337 \&\fB\-max_protocol\fR instead.
338 .IP "\fB\-anti_replay\fR, \fB\-no_anti_replay\fR" 4
339 .IX Item "-anti_replay, -no_anti_replay"
340 Switches replay protection, on or off respectively. With replay protection on,
341 OpenSSL will automatically detect if a session ticket has been used more than
342 once, TLSv1.3 has been negotiated, and early data is enabled on the server. A
343 full handshake is forced if a session ticket is used a second or subsequent
344 time. Anti-Replay is on by default unless overridden by a configuration file and
345 is only used by servers. Anti-replay measures are required for compliance with
346 the TLSv1.3 specification. Some applications may be able to mitigate the replay
347 risks in other ways and in such cases the built-in OpenSSL functionality is not
348 required. Switching off anti-replay is equivalent to \fBSSL_OP_NO_ANTI_REPLAY\fR.
349 .SH "SUPPORTED CONFIGURATION FILE COMMANDS"
350 .IX Header "SUPPORTED CONFIGURATION FILE COMMANDS"
351 Currently supported \fBoption\fR names for configuration files (i.e., when the
352 flag \fBSSL_CONF_FLAG_FILE\fR is set) are listed below. All configuration file
353 \&\fBoption\fR names are case insensitive so \fBsignaturealgorithms\fR is recognised
354 as well as \fBSignatureAlgorithms\fR. Unless otherwise stated the \fBvalue\fR names
355 are also case insensitive.
356 .PP
357 Note: the command prefix (if set) alters the recognised \fBoption\fR values.
358 .IP \fBCipherString\fR 4
359 .IX Item "CipherString"
360 Sets the ciphersuite list for TLSv1.2 and below to \fBvalue\fR. This list will be
361 combined with any configured TLSv1.3 ciphersuites. Note: syntax
362 checking of \fBvalue\fR is currently not performed unless an \fBSSL\fR or \fBSSL_CTX\fR
363 structure is associated with \fBctx\fR.
364 .IP \fBCiphersuites\fR 4
365 .IX Item "Ciphersuites"
366 Sets the available ciphersuites for TLSv1.3 to \fBvalue\fR. This is a
367 colon-separated list of TLSv1.3 ciphersuite names in order of preference. This
368 list will be combined any configured TLSv1.2 and below ciphersuites.
369 See \fBopenssl\-ciphers\fR\|(1) for more information.
370 .IP \fBCertificate\fR 4
371 .IX Item "Certificate"
372 Attempts to use the file \fBvalue\fR as the certificate for the appropriate
373 context. It currently uses \fBSSL_CTX_use_certificate_chain_file()\fR if an \fBSSL_CTX\fR
374 structure is set or \fBSSL_use_certificate_file()\fR with filetype PEM if an \fBSSL\fR
375 structure is set. This option is only supported if certificate operations
376 are permitted.
377 .IP \fBPrivateKey\fR 4
378 .IX Item "PrivateKey"
379 Attempts to use the file \fBvalue\fR as the private key for the appropriate
380 context. This option is only supported if certificate operations
381 are permitted. Note: if no \fBPrivateKey\fR option is set then a private key is
382 not loaded unless the \fBSSL_CONF_FLAG_REQUIRE_PRIVATE\fR is set.
383 .IP "\fBChainCAFile\fR, \fBChainCAPath\fR, \fBVerifyCAFile\fR, \fBVerifyCAPath\fR" 4
384 .IX Item "ChainCAFile, ChainCAPath, VerifyCAFile, VerifyCAPath"
385 These options indicate a file or directory used for building certificate
386 chains or verifying certificate chains. These options are only supported
387 if certificate operations are permitted.
388 .IP \fBRequestCAFile\fR 4
389 .IX Item "RequestCAFile"
390 This option indicates a file containing a set of certificates in PEM form.
391 The subject names of the certificates are sent to the peer in the
392 \&\fBcertificate_authorities\fR extension for TLS 1.3 (in ClientHello or
393 CertificateRequest) or in a certificate request for previous versions or
394 TLS.
395 .IP \fBServerInfoFile\fR 4
396 .IX Item "ServerInfoFile"
397 Attempts to use the file \fBvalue\fR in the "serverinfo" extension using the
398 function SSL_CTX_use_serverinfo_file.
399 .IP \fBDHParameters\fR 4
400 .IX Item "DHParameters"
401 Attempts to use the file \fBvalue\fR as the set of temporary DH parameters for
402 the appropriate context. This option is only supported if certificate
403 operations are permitted.
404 .IP \fBRecordPadding\fR 4
405 .IX Item "RecordPadding"
406 Controls use of TLSv1.3 record layer padding. \fBvalue\fR is a string of the form
407 "number[,number]" where the (required) first number is the padding block size
408 (in octets) for application data, and the optional second number is the padding
409 block size for handshake and alert messages. If the optional second number is
410 omitted, the same padding will be applied to all messages.
411 .Sp
412 Padding attempts to pad TLSv1.3 records so that they are a multiple of the set
413 length on send. A value of 0 or 1 turns off padding as relevant. Otherwise, the
414 values must be >1 or <=16384.
415 .Sp
416 Note that, for QUIC objects, padding is always performed at the
417 packet level, and so cannot be done at the record level. Given that, when the
418 config file is created, there is no knowledge of what kind of SSL objects are
419 being created, this option is silently ignored for QUIC objects.
420 .IP \fBSignatureAlgorithms\fR 4
421 .IX Item "SignatureAlgorithms"
422 This sets the supported signature algorithms for TLSv1.2 and TLSv1.3.
423 For clients this
424 value is used directly for the supported signature algorithms extension. For
425 servers it is used to determine which signature algorithms to support.
426 .Sp
427 The \fBvalue\fR argument should be a colon separated list of signature algorithms
428 in order of decreasing preference of the form \fBalgorithm+hash\fR or
429 \&\fBsignature_scheme\fR. For the default providers shipped with OpenSSL,
430 \&\fBalgorithm\fR is one of \fBRSA\fR, \fBDSA\fR or \fBECDSA\fR and \fBhash\fR is a supported
431 algorithm OID short name such as \fBSHA1\fR, \fBSHA224\fR, \fBSHA256\fR, \fBSHA384\fR
432 or \fBSHA512\fR.
433 \&\fBsignature_scheme\fR is one of the signature schemes defined in TLSv1.3,
434 specified using the IANA name, e.g., \fBecdsa_secp256r1_sha256\fR, \fBed25519\fR,
435 or \fBrsa_pss_pss_sha256\fR.
436 Signature scheme names and public key algorithm names (but not the hash names)
437 in the \fBalgorithm+hash\fR form are case-insensitive.
438 Additional providers may make available further signature schemes via the
439 TLS_SIGALG capability. See "CAPABILITIES" in \fBprovider\-base\fR\|(7).
440 .Sp
441 If this option is not set then all signature algorithms supported by all
442 activated providers are permissible.
443 .Sp
444 Note: algorithms which specify a PKCS#1 v1.5 signature scheme (either by
445 using \fBRSA\fR as the \fBalgorithm\fR or by using one of the \fBrsa_pkcs1_*\fR
446 identifiers) are ignored in TLSv1.3 and will not be negotiated.
447 .IP \fBClientSignatureAlgorithms\fR 4
448 .IX Item "ClientSignatureAlgorithms"
449 This sets the supported signature algorithms associated with client
450 authentication for TLSv1.2 and TLSv1.3.
451 For servers the value is used in the
452 \&\fBsignature_algorithms\fR field of a \fBCertificateRequest\fR message.
453 For clients it is
454 used to determine which signature algorithm to use with the client certificate.
455 If a server does not request a certificate this option has no effect.
456 .Sp
457 The syntax of \fBvalue\fR is identical to \fBSignatureAlgorithms\fR. If not set then
458 the value set for \fBSignatureAlgorithms\fR will be used instead.
459 .IP \fBGroups\fR 4
460 .IX Item "Groups"
461 This sets the supported groups. For clients, the groups are
462 sent using the supported groups extension. For servers, it is used
463 to determine which group to use. This setting affects groups used for
464 signatures (in TLSv1.2 and earlier) and key exchange. The first group listed
465 will also be used for the \fBkey_share\fR sent by a client in a TLSv1.3
466 \&\fBClientHello\fR.
467 .Sp
468 The \fBgroups\fR argument is a colon separated list of groups. The preferred
469 names are those listed in the IANA
470 TLS Supported Groups <https://www.iana.org/assignments/tls-parameters/tls-parameters.xhtml#tls-parameters-8>
471 registry.
472 For some groups, OpenSSL supports additional aliases.
473 Such an alias could be a \fBNIST\fR name (e.g. \fBP\-256\fR), an OpenSSL OID name
474 (e.g. \fBprime256v1\fR), or some other commonly used name.
475 Group names are case-insensitive in OpenSSL 3.5 and later.
476 The list should be in order of preference with the most preferred group first.
477 .Sp
478 The commands below list the available groups for TLS 1.2 and TLS 1.3,
479 respectively:
480 .Sp
481 .Vb 2
482 \& $ openssl list \-tls1_2 \-tls\-groups
483 \& $ openssl list \-tls1_3 \-tls\-groups
484 .Ve
485 .Sp
486 An enriched alternative syntax, that enables clients to send multiple keyshares
487 and allows servers to prioritise some groups over others, is described in
488 \&\fBSSL_CTX_set1_groups_list\fR\|(3).
489 Since TLS 1.2 has neither keyshares nor a hello retry mechanism, with TLS 1.2
490 the enriched syntax is ultimately equivalent to just a simple ordered list of
491 groups, as with the simple form above.
492 .IP \fBCurves\fR 4
493 .IX Item "Curves"
494 This is a synonym for the "Groups" command.
495 .IP \fBMinProtocol\fR 4
496 .IX Item "MinProtocol"
497 This sets the minimum supported SSL, TLS or DTLS version.
498 .Sp
499 Currently supported protocol values are \fBSSLv3\fR, \fBTLSv1\fR, \fBTLSv1.1\fR,
500 \&\fBTLSv1.2\fR, \fBTLSv1.3\fR, \fBDTLSv1\fR and \fBDTLSv1.2\fR.
501 The SSL and TLS bounds apply only to TLS-based contexts, while the DTLS bounds
502 apply only to DTLS-based contexts.
503 The command can be repeated with one instance setting a TLS bound, and the
504 other setting a DTLS bound.
505 The value \fBNone\fR applies to both types of contexts and disables the limits.
506 .IP \fBMaxProtocol\fR 4
507 .IX Item "MaxProtocol"
508 This sets the maximum supported SSL, TLS or DTLS version.
509 .Sp
510 Currently supported protocol values are \fBSSLv3\fR, \fBTLSv1\fR, \fBTLSv1.1\fR,
511 \&\fBTLSv1.2\fR, \fBTLSv1.3\fR, \fBDTLSv1\fR and \fBDTLSv1.2\fR.
512 The SSL and TLS bounds apply only to TLS-based contexts, while the DTLS bounds
513 apply only to DTLS-based contexts.
514 The command can be repeated with one instance setting a TLS bound, and the
515 other setting a DTLS bound.
516 The value \fBNone\fR applies to both types of contexts and disables the limits.
517 .IP \fBProtocol\fR 4
518 .IX Item "Protocol"
519 This can be used to enable or disable certain versions of the SSL,
520 TLS or DTLS protocol.
521 .Sp
522 The \fBvalue\fR argument is a comma separated list of supported protocols
523 to enable or disable.
524 If a protocol is preceded by \fB\-\fR that version is disabled.
525 .Sp
526 All protocol versions are enabled by default.
527 You need to disable at least one protocol version for this setting have any
528 effect.
529 Only enabling some protocol versions does not disable the other protocol
530 versions.
531 .Sp
532 Currently supported protocol values are \fBSSLv3\fR, \fBTLSv1\fR, \fBTLSv1.1\fR,
533 \&\fBTLSv1.2\fR, \fBTLSv1.3\fR, \fBDTLSv1\fR and \fBDTLSv1.2\fR.
534 The special value \fBALL\fR refers to all supported versions.
535 .Sp
536 This can't enable protocols that are disabled using \fBMinProtocol\fR
537 or \fBMaxProtocol\fR, but can disable protocols that are still allowed
538 by them.
539 .Sp
540 The \fBProtocol\fR command is fragile and deprecated; do not use it.
541 Use \fBMinProtocol\fR and \fBMaxProtocol\fR instead.
542 If you do use \fBProtocol\fR, make sure that the resulting range of enabled
543 protocols has no "holes", e.g. if TLS 1.0 and TLS 1.2 are both enabled, make
544 sure to also leave TLS 1.1 enabled.
545 .IP \fBOptions\fR 4
546 .IX Item "Options"
547 The \fBvalue\fR argument is a comma separated list of various flags to set.
548 If a flag string is preceded \fB\-\fR it is disabled.
549 See the \fBSSL_CTX_set_options\fR\|(3) function for more details of
550 individual options.
551 .Sp
552 Each option is listed below. Where an operation is enabled by default
553 the \fB\-flag\fR syntax is needed to disable it.
554 .Sp
555 \&\fBSessionTicket\fR: session ticket support, enabled by default. Inverse of
556 \&\fBSSL_OP_NO_TICKET\fR: that is \fB\-SessionTicket\fR is the same as setting
557 \&\fBSSL_OP_NO_TICKET\fR.
558 .Sp
559 \&\fBCompression\fR: SSL/TLS compression support, disabled by default. Inverse
560 of \fBSSL_OP_NO_COMPRESSION\fR.
561 .Sp
562 \&\fBEmptyFragments\fR: use empty fragments as a countermeasure against a
563 SSL 3.0/TLS 1.0 protocol vulnerability affecting CBC ciphers. It
564 is set by default. Inverse of \fBSSL_OP_DONT_INSERT_EMPTY_FRAGMENTS\fR.
565 .Sp
566 \&\fBBugs\fR: enable various bug workarounds. Same as \fBSSL_OP_ALL\fR.
567 .Sp
568 \&\fBDHSingle\fR: enable single use DH keys, set by default. Inverse of
569 \&\fBSSL_OP_DH_SINGLE\fR. Only used by servers.
570 .Sp
571 \&\fBECDHSingle\fR: enable single use ECDH keys, set by default. Inverse of
572 \&\fBSSL_OP_ECDH_SINGLE\fR. Only used by servers.
573 .Sp
574 \&\fBServerPreference\fR: use server and not client preference order when
575 determining which cipher suite, signature algorithm or elliptic curve
576 to use for an incoming connection. Equivalent to
577 \&\fBSSL_OP_CIPHER_SERVER_PREFERENCE\fR. Only used by servers.
578 .Sp
579 \&\fBPrioritizeChaCha\fR: prioritizes ChaCha ciphers when the client has a
580 ChaCha20 cipher at the top of its preference list. This usually indicates
581 a mobile client is in use. Equivalent to \fBSSL_OP_PRIORITIZE_CHACHA\fR.
582 Only used by servers.
583 .Sp
584 \&\fBNoResumptionOnRenegotiation\fR: set
585 \&\fBSSL_OP_NO_SESSION_RESUMPTION_ON_RENEGOTIATION\fR flag. Only used by servers.
586 .Sp
587 \&\fBNoRenegotiation\fR: disables all attempts at renegotiation in TLSv1.2 and
588 earlier, same as setting \fBSSL_OP_NO_RENEGOTIATION\fR.
589 .Sp
590 \&\fBUnsafeLegacyRenegotiation\fR: permits the use of unsafe legacy renegotiation.
591 Equivalent to \fBSSL_OP_ALLOW_UNSAFE_LEGACY_RENEGOTIATION\fR.
592 .Sp
593 \&\fBUnsafeLegacyServerConnect\fR: permits the use of unsafe legacy renegotiation
594 for OpenSSL clients only. Equivalent to \fBSSL_OP_LEGACY_SERVER_CONNECT\fR.
595 .Sp
596 \&\fBEncryptThenMac\fR: use encrypt-then-mac extension, enabled by
597 default. Inverse of \fBSSL_OP_NO_ENCRYPT_THEN_MAC\fR: that is,
598 \&\fB\-EncryptThenMac\fR is the same as setting \fBSSL_OP_NO_ENCRYPT_THEN_MAC\fR.
599 .Sp
600 \&\fBAllowNoDHEKEX\fR: In TLSv1.3 allow a non\-(ec)dhe based key exchange mode on
601 resumption. This means that there will be no forward secrecy for the resumed
602 session. Equivalent to \fBSSL_OP_ALLOW_NO_DHE_KEX\fR.
603 .Sp
604 \&\fBPreferNoDHEKEX\fR: In TLSv1.3, on resumption let the server prefer a
605 non\-(ec)dhe based key exchange mode over an (ec)dhe based one. Requires
606 \&\fBAllowNoDHEKEX\fR. Equivalent to \fBSSL_OP_PREFER_NO_DHE_KEX\fR. Only used by
607 servers.
608 .Sp
609 \&\fBMiddleboxCompat\fR: If set then dummy Change Cipher Spec (CCS) messages are sent
610 in TLSv1.3. This has the effect of making TLSv1.3 look more like TLSv1.2 so that
611 middleboxes that do not understand TLSv1.3 will not drop the connection. This
612 option is set by default. A future version of OpenSSL may not set this by
613 default. Equivalent to \fBSSL_OP_ENABLE_MIDDLEBOX_COMPAT\fR.
614 .Sp
615 \&\fBAntiReplay\fR: If set then OpenSSL will automatically detect if a session ticket
616 has been used more than once, TLSv1.3 has been negotiated, and early data is
617 enabled on the server. A full handshake is forced if a session ticket is used a
618 second or subsequent time. This option is set by default and is only used by
619 servers. Anti-replay measures are required to comply with the TLSv1.3
620 specification. Some applications may be able to mitigate the replay risks in
621 other ways and in such cases the built-in OpenSSL functionality is not required.
622 Disabling anti-replay is equivalent to setting \fBSSL_OP_NO_ANTI_REPLAY\fR.
623 .Sp
624 \&\fBExtendedMasterSecret\fR: use extended master secret extension, enabled by
625 default. Inverse of \fBSSL_OP_NO_EXTENDED_MASTER_SECRET\fR: that is,
626 \&\fB\-ExtendedMasterSecret\fR is the same as setting \fBSSL_OP_NO_EXTENDED_MASTER_SECRET\fR.
627 .Sp
628 \&\fBCANames\fR: use CA names extension, enabled by
629 default. Inverse of \fBSSL_OP_DISABLE_TLSEXT_CA_NAMES\fR: that is,
630 \&\fB\-CANames\fR is the same as setting \fBSSL_OP_DISABLE_TLSEXT_CA_NAMES\fR.
631 .Sp
632 \&\fBKTLS\fR: Enables kernel TLS if support has been compiled in, and it is supported
633 by the negotiated ciphersuites and extensions. Equivalent to
634 \&\fBSSL_OP_ENABLE_KTLS\fR.
635 .Sp
636 \&\fBStrictCertCheck\fR: Enable strict certificate checking. Equivalent to
637 setting \fBSSL_CERT_FLAG_TLS_STRICT\fR with \fBSSL_CTX_set_cert_flags()\fR.
638 .Sp
639 \&\fBTxCertificateCompression\fR: support sending compressed certificates, enabled by
640 default. Inverse of \fBSSL_OP_NO_TX_CERTIFICATE_COMPRESSION\fR: that is,
641 \&\fB\-TxCertificateCompression\fR is the same as setting \fBSSL_OP_NO_TX_CERTIFICATE_COMPRESSION\fR.
642 .Sp
643 \&\fBRxCertificateCompression\fR: support receiving compressed certificates, enabled by
644 default. Inverse of \fBSSL_OP_NO_RX_CERTIFICATE_COMPRESSION\fR: that is,
645 \&\fB\-RxCertificateCompression\fR is the same as setting \fBSSL_OP_NO_RX_CERTIFICATE_COMPRESSION\fR.
646 .Sp
647 \&\fBKTLSTxZerocopySendfile\fR: use the zerocopy TX mode of \fBsendfile()\fR, which gives
648 a performance boost when used with KTLS hardware offload. Note that invalid TLS
649 records might be transmitted if the file is changed while being sent. This
650 option has no effect if \fBKTLS\fR is not enabled. Equivalent to
651 \&\fBSSL_OP_ENABLE_KTLS_TX_ZEROCOPY_SENDFILE\fR. This option only applies to Linux.
652 KTLS sendfile on FreeBSD doesn't offer an option to disable zerocopy and
653 always runs in this mode.
654 .Sp
655 \&\fBIgnoreUnexpectedEOF\fR: Equivalent to \fBSSL_OP_IGNORE_UNEXPECTED_EOF\fR.
656 You should only enable this option if the protocol running over TLS can detect
657 a truncation attack itself, and that the application is checking for that
658 truncation attack.
659 .IP \fBVerifyMode\fR 4
660 .IX Item "VerifyMode"
661 The \fBvalue\fR argument is a comma separated list of flags to set.
662 .Sp
663 \&\fBPeer\fR enables peer verification: for clients only.
664 .Sp
665 \&\fBRequest\fR requests but does not require a certificate from the client.
666 Servers only.
667 .Sp
668 \&\fBRequire\fR requests and requires a certificate from the client: an error
669 occurs if the client does not present a certificate. Servers only.
670 .Sp
671 \&\fBOnce\fR requests a certificate from a client only on the initial connection:
672 not when renegotiating. Servers only.
673 .Sp
674 \&\fBRequestPostHandshake\fR configures the connection to support requests but does
675 not require a certificate from the client post-handshake. A certificate will
676 not be requested during the initial handshake. The server application must
677 provide a mechanism to request a certificate post-handshake. Servers only.
678 TLSv1.3 only.
679 .Sp
680 \&\fBRequiresPostHandshake\fR configures the connection to support requests and
681 requires a certificate from the client post-handshake: an error occurs if the
682 client does not present a certificate. A certificate will not be requested
683 during the initial handshake. The server application must provide a mechanism
684 to request a certificate post-handshake. Servers only. TLSv1.3 only.
685 .IP "\fBClientCAFile\fR, \fBClientCAPath\fR" 4
686 .IX Item "ClientCAFile, ClientCAPath"
687 A file or directory of certificates in PEM format whose names are used as the
688 set of acceptable names for client CAs. Servers only. This option is only
689 supported if certificate operations are permitted.
690 .SH "SUPPORTED COMMAND TYPES"
691 .IX Header "SUPPORTED COMMAND TYPES"
692 The function \fBSSL_CONF_cmd_value_type()\fR currently returns one of the following
693 types:
694 .IP \fBSSL_CONF_TYPE_UNKNOWN\fR 4
695 .IX Item "SSL_CONF_TYPE_UNKNOWN"
696 The \fBoption\fR string is unrecognised, this return value can be use to flag
697 syntax errors.
698 .IP \fBSSL_CONF_TYPE_STRING\fR 4
699 .IX Item "SSL_CONF_TYPE_STRING"
700 The value is a string without any specific structure.
701 .IP \fBSSL_CONF_TYPE_FILE\fR 4
702 .IX Item "SSL_CONF_TYPE_FILE"
703 The value is a filename.
704 .IP \fBSSL_CONF_TYPE_DIR\fR 4
705 .IX Item "SSL_CONF_TYPE_DIR"
706 The value is a directory name.
707 .IP \fBSSL_CONF_TYPE_NONE\fR 4
708 .IX Item "SSL_CONF_TYPE_NONE"
709 The value string is not used e.g. a command line option which doesn't take an
710 argument.
711 .SH NOTES
712 .IX Header "NOTES"
713 The order of operations is significant. This can be used to set either defaults
714 or values which cannot be overridden. For example if an application calls:
715 .PP
716 .Vb 2
717 \& SSL_CONF_cmd(ctx, "Protocol", "\-SSLv3");
718 \& SSL_CONF_cmd(ctx, userparam, uservalue);
719 .Ve
720 .PP
721 it will disable SSLv3 support by default but the user can override it. If
722 however the call sequence is:
723 .PP
724 .Vb 2
725 \& SSL_CONF_cmd(ctx, userparam, uservalue);
726 \& SSL_CONF_cmd(ctx, "Protocol", "\-SSLv3");
727 .Ve
728 .PP
729 SSLv3 is \fBalways\fR disabled and attempt to override this by the user are
730 ignored.
731 .PP
732 By checking the return code of \fBSSL_CONF_cmd()\fR it is possible to query if a
733 given \fBoption\fR is recognised, this is useful if \fBSSL_CONF_cmd()\fR values are
734 mixed with additional application specific operations.
735 .PP
736 For example an application might call \fBSSL_CONF_cmd()\fR and if it returns
737 \&\-2 (unrecognised command) continue with processing of application specific
738 commands.
739 .PP
740 Applications can also use \fBSSL_CONF_cmd()\fR to process command lines though the
741 utility function \fBSSL_CONF_cmd_argv()\fR is normally used instead. One way
742 to do this is to set the prefix to an appropriate value using
743 \&\fBSSL_CONF_CTX_set1_prefix()\fR, pass the current argument to \fBoption\fR and the
744 following argument to \fBvalue\fR (which may be NULL).
745 .PP
746 In this case if the return value is positive then it is used to skip that
747 number of arguments as they have been processed by \fBSSL_CONF_cmd()\fR. If \-2 is
748 returned then \fBoption\fR is not recognised and application specific arguments
749 can be checked instead. If \-3 is returned a required argument is missing
750 and an error is indicated. If 0 is returned some other error occurred and
751 this can be reported back to the user.
752 .PP
753 The function \fBSSL_CONF_cmd_value_type()\fR can be used by applications to
754 check for the existence of a command or to perform additional syntax
755 checking or translation of the command value. For example if the return
756 value is \fBSSL_CONF_TYPE_FILE\fR an application could translate a relative
757 pathname to an absolute pathname.
758 .SH "RETURN VALUES"
759 .IX Header "RETURN VALUES"
760 \&\fBSSL_CONF_cmd()\fR returns 1 if the value of \fBoption\fR is recognised and \fBvalue\fR is
761 \&\fBNOT\fR used and 2 if both \fBoption\fR and \fBvalue\fR are used. In other words it
762 returns the number of arguments processed. This is useful when processing
763 command lines.
764 .PP
765 A return value of \-2 means \fBoption\fR is not recognised.
766 .PP
767 A return value of \-3 means \fBoption\fR is recognised and the command requires a
768 value but \fBvalue\fR is NULL.
769 .PP
770 A return code of 0 indicates that both \fBoption\fR and \fBvalue\fR are valid but an
771 error occurred attempting to perform the operation: for example due to an
772 error in the syntax of \fBvalue\fR in this case the error queue may provide
773 additional information.
774 .SH EXAMPLES
775 .IX Header "EXAMPLES"
776 Set supported signature algorithms:
777 .PP
778 .Vb 1
779 \& SSL_CONF_cmd(ctx, "SignatureAlgorithms", "ECDSA+SHA256:RSA+SHA256:DSA+SHA256");
780 .Ve
781 .PP
782 There are various ways to select the supported protocols.
783 .PP
784 This set the minimum protocol version to TLSv1, and so disables SSLv3.
785 This is the recommended way to disable protocols.
786 .PP
787 .Vb 1
788 \& SSL_CONF_cmd(ctx, "MinProtocol", "TLSv1");
789 .Ve
790 .PP
791 The following also disables SSLv3:
792 .PP
793 .Vb 1
794 \& SSL_CONF_cmd(ctx, "Protocol", "\-SSLv3");
795 .Ve
796 .PP
797 The following will first enable all protocols, and then disable
798 SSLv3.
799 If no protocol versions were disabled before this has the same effect as
800 "\-SSLv3", but if some versions were disables this will re-enable them before
801 disabling SSLv3.
802 .PP
803 .Vb 1
804 \& SSL_CONF_cmd(ctx, "Protocol", "ALL,\-SSLv3");
805 .Ve
806 .PP
807 Only enable TLSv1.2:
808 .PP
809 .Vb 2
810 \& SSL_CONF_cmd(ctx, "MinProtocol", "TLSv1.2");
811 \& SSL_CONF_cmd(ctx, "MaxProtocol", "TLSv1.2");
812 .Ve
813 .PP
814 This also only enables TLSv1.2:
815 .PP
816 .Vb 1
817 \& SSL_CONF_cmd(ctx, "Protocol", "\-ALL,TLSv1.2");
818 .Ve
819 .PP
820 Disable TLS session tickets:
821 .PP
822 .Vb 1
823 \& SSL_CONF_cmd(ctx, "Options", "\-SessionTicket");
824 .Ve
825 .PP
826 Enable compression:
827 .PP
828 .Vb 1
829 \& SSL_CONF_cmd(ctx, "Options", "Compression");
830 .Ve
831 .PP
832 Set supported curves to P\-256, P\-384:
833 .PP
834 .Vb 1
835 \& SSL_CONF_cmd(ctx, "Curves", "P\-256:P\-384");
836 .Ve
837 .SH "SEE ALSO"
838 .IX Header "SEE ALSO"
839 \&\fBssl\fR\|(7),
840 \&\fBSSL_CONF_CTX_new\fR\|(3),
841 \&\fBSSL_CONF_CTX_set_flags\fR\|(3),
842 \&\fBSSL_CONF_CTX_set1_prefix\fR\|(3),
843 \&\fBSSL_CONF_CTX_set_ssl_ctx\fR\|(3),
844 \&\fBSSL_CONF_cmd_argv\fR\|(3),
845 \&\fBSSL_CTX_set_options\fR\|(3)
846 .SH HISTORY
847 .IX Header "HISTORY"
848 The \fBSSL_CONF_cmd()\fR function was added in OpenSSL 1.0.2.
849 .PP
850 The \fBSSL_OP_NO_SSL2\fR option doesn't have effect since 1.1.0, but the macro
851 is retained for backwards compatibility.
852 .PP
853 The \fBSSL_CONF_TYPE_NONE\fR was added in OpenSSL 1.1.0. In earlier versions of
854 OpenSSL passing a command which didn't take an argument would return
855 \&\fBSSL_CONF_TYPE_UNKNOWN\fR.
856 .PP
857 \&\fBMinProtocol\fR and \fBMaxProtocol\fR where added in OpenSSL 1.1.0.
858 .PP
859 \&\fBAllowNoDHEKEX\fR and \fBPrioritizeChaCha\fR were added in OpenSSL 1.1.1.
860 .PP
861 The \fBUnsafeLegacyServerConnect\fR option is no longer set by default from
862 OpenSSL 3.0.
863 .PP
864 The \fBTxCertificateCompression\fR and \fBRxCertificateCompression\fR options were
865 added in OpenSSL 3.2.
866 .PP
867 \&\fBPreferNoDHEKEX\fR was added in OpenSSL 3.3.
868 .PP
869 OpenSSL 3.5 introduces support for post-quantum (PQ) TLS key exchange via the
870 \&\fBMLKEM512\fR, \fBMLKEM768\fR and \fBMLKEM1024\fR TLS groups.
871 These are based on the underlying \fBML\-KEM\-512\fR, \fBML\-KEM\-768\fR and
872 \&\fBML\-KEM\-1024\fR algorithms from FIPS 203.
873 .PP
874 OpenSSL 3.5 also introduces support for three \fBhybrid\fR ECDH PQ key exchange
875 TLS groups: \fBX25519MLKEM768\fR, \fBSecP256r1MLKEM768\fR and
876 \&\fBSecP384r1MLKEM1024\fR.
877 They offer CPU performance comparable to the associated ECDH group, though at
878 the cost of significantly larger key exchange messages.
879 The third group, \fBSecP384r1MLKEM1024\fR is substantially more CPU-intensive,
880 largely as a result of the high CPU cost of ECDH for the underlying \fBP\-384\fR
881 group.
882 Also its key exchange messages at close to 1700 bytes are larger than the
883 roughly 1200 bytes for the first two groups.
884 .PP
885 As of OpenSSL 3.5 key exchange group names are case-insensitive.
886 .SH COPYRIGHT
887 .IX Header "COPYRIGHT"
888 Copyright 2012\-2026 The OpenSSL Project Authors. All Rights Reserved.
889 .PP
890 Licensed under the Apache License 2.0 (the "License"). You may not use
891 this file except in compliance with the License. You can obtain a copy
892 in the file LICENSE in the source distribution or at
893 <https://www.openssl.org/source/license.html>.