Automatically generated by Pod::Man 4.14 (Pod::Simple 3.40)

Standard preamble:
========================================================================
..

..

.. Set up some character translations and predefined strings. \*(-- will
give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
double quote, and \*(R" will give a right double quote. \*(C+ will
give a nicer C++. Capital omega is used to do unbreakable dashes and
therefore won't be available. \*(C` and \*(C' expand to `' in nroff,
nothing in troff, for use with C<>.
.tr \(*W- . ds -- \(*W- . ds PI pi . if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch . if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch . ds L" "" . ds R" "" . ds C` "" . ds C' "" 'br\} . ds -- \|\(em\| . ds PI \(*p . ds L" `` . ds R" '' . 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
Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
Fear. Run. Save yourself. No user-serviceable parts.
. \" fudge factors for nroff and troff . ds #H 0 . ds #V .8m . ds #F .3m . ds #[ \f1 . ds #] .\} . ds #H ((1u-(\\\\n(.fu%2u))*.13m) . ds #V .6m . ds #F 0 . ds #[ \& . ds #] \& .\} . \" simple accents for nroff and troff . ds ' \& . ds ` \& . ds ^ \& . ds , \& . ds ~ ~ . ds / .\} . ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u" . ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u' . ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u' . ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u' . ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u' . ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u' .\} . \" troff and (daisy-wheel) nroff accents . \" corrections for vroff . \" for low resolution devices (crt and lpr) \{\ . ds : e . ds 8 ss . ds o a . ds d- d\h'-1'\(ga . ds D- D\h'-1'\(hy . ds th \o'bp' . ds Th \o'LP' . ds ae ae . ds Ae AE .\} ========================================================================

Title "SSL_CTX_SET_OPTIONS 3" For nroff, turn off justification. Always turn off hyphenation; it makes
way too many mistakes in technical documents.
SSL_CTX_set_options, SSL_set_options, SSL_CTX_clear_options, SSL_clear_options, SSL_CTX_get_options, SSL_get_options, SSL_get_secure_renegotiation_support - manipulate SSL options Header "SYNOPSIS" .Vb 1 #include <openssl/ssl.h> \& long SSL_CTX_set_options(SSL_CTX *ctx, long options); long SSL_set_options(SSL *ssl, long options); \& long SSL_CTX_clear_options(SSL_CTX *ctx, long options); long SSL_clear_options(SSL *ssl, long options); \& long SSL_CTX_get_options(SSL_CTX *ctx); long SSL_get_options(SSL *ssl); \& long SSL_get_secure_renegotiation_support(SSL *ssl); .Ve Header "DESCRIPTION" \fBSSL_CTX_set_options() adds the options set via bit mask in options to ctx. Options already set before are not cleared!

\fBSSL_set_options() adds the options set via bit mask in options to ssl. Options already set before are not cleared!

\fBSSL_CTX_clear_options() clears the options set via bit mask in options to ctx.

\fBSSL_clear_options() clears the options set via bit mask in options to ssl.

\fBSSL_CTX_get_options() returns the options set for ctx.

\fBSSL_get_options() returns the options set for ssl.

\fBSSL_get_secure_renegotiation_support() indicates whether the peer supports secure renegotiation. Note, this is implemented via a macro.

Header "NOTES" The behaviour of the \s-1SSL\s0 library can be changed by setting several options. The options are coded as bit masks and can be combined by a bitwise or operation (|).

\fBSSL_CTX_set_options() and SSL_set_options() affect the (external) protocol behaviour of the \s-1SSL\s0 library. The (internal) behaviour of the \s-1API\s0 can be changed by using the similar \fBSSL_CTX_set_mode\|(3) and SSL_set_mode() functions.

During a handshake, the option settings of the \s-1SSL\s0 object are used. When a new \s-1SSL\s0 object is created from a context using SSL_new(), the current option setting is copied. Changes to ctx do not affect already created \s-1SSL\s0 objects. SSL_clear() does not affect the settings.

The following bug workaround options are available:

Item "SSL_OP_SAFARI_ECDHE_ECDSA_BUG" Don't prefer ECDHE-ECDSA ciphers when the client appears to be Safari on \s-1OS X. OS X 10.8..10.8.3\s0 has broken support for ECDHE-ECDSA ciphers. Item "SSL_OP_DONT_INSERT_EMPTY_FRAGMENTS" Disables a countermeasure against a \s-1SSL 3.0/TLS 1.0\s0 protocol vulnerability affecting \s-1CBC\s0 ciphers, which cannot be handled by some broken \s-1SSL\s0 implementations. This option has no effect for connections using other ciphers. Item "SSL_OP_TLSEXT_PADDING" Adds a padding extension to ensure the ClientHello size is never between 256 and 511 bytes in length. This is needed as a workaround for some implementations. Item "SSL_OP_ALL" All of the above bug workarounds plus \s-1SSL_OP_LEGACY_SERVER_CONNECT\s0 as mentioned below.

It is usually safe to use \s-1SSL_OP_ALL\s0 to enable the bug workaround options if compatibility with somewhat broken implementations is desired.

The following modifying options are available:

Item "SSL_OP_TLS_ROLLBACK_BUG" Disable version rollback attack detection. .Sp During the client key exchange, the client must send the same information about acceptable \s-1SSL/TLS\s0 protocol levels as during the first hello. Some clients violate this rule by adapting to the server's answer. (Example: the client sends a SSLv2 hello and accepts up to SSLv3.1=TLSv1, the server only understands up to SSLv3. In this case the client must still use the same SSLv3.1=TLSv1 announcement. Some clients step down to SSLv3 with respect to the server's answer and violate the version rollback protection.) Item "SSL_OP_CIPHER_SERVER_PREFERENCE" When choosing a cipher, use the server's preferences instead of the client preferences. When not set, the \s-1SSL\s0 server will always follow the clients preferences. When set, the \s-1SSL/TLS\s0 server will choose following its own preferences. Item "SSL_OP_NO_SSLv3, SSL_OP_NO_TLSv1, SSL_OP_NO_TLSv1_1, SSL_OP_NO_TLSv1_2, SSL_OP_NO_TLSv1_3, SSL_OP_NO_DTLSv1, SSL_OP_NO_DTLSv1_2" These options turn off the SSLv3, TLSv1, TLSv1.1, TLSv1.2 or TLSv1.3 protocol versions with \s-1TLS\s0 or the DTLSv1, DTLSv1.2 versions with \s-1DTLS,\s0 respectively. As of OpenSSL 1.1.0, these options are deprecated, use \fBSSL_CTX_set_min_proto_version\|(3) and \fBSSL_CTX_set_max_proto_version\|(3) instead. Item "SSL_OP_NO_SESSION_RESUMPTION_ON_RENEGOTIATION" When performing renegotiation as a server, always start a new session (i.e., session resumption requests are only accepted in the initial handshake). This option is not needed for clients. Item "SSL_OP_NO_COMPRESSION" Do not use compression even if it is supported. Item "SSL_OP_NO_QUERY_MTU" Do not query the \s-1MTU.\s0 Only affects \s-1DTLS\s0 connections. Item "SSL_OP_COOKIE_EXCHANGE" Turn on Cookie Exchange as described in \s-1RFC4347\s0 Section 4.2.1. Only affects \s-1DTLS\s0 connections. Item "SSL_OP_NO_TICKET" \s-1SSL/TLS\s0 supports two mechanisms for resuming sessions: session ids and stateless session tickets. .Sp When using session ids a copy of the session information is cached on the server and a unique id is sent to the client. When the client wishes to resume it provides the unique id so that the server can retrieve the session information from its cache. .Sp When using stateless session tickets the server uses a session ticket encryption key to encrypt the session information. This encrypted data is sent to the client as a \*(L"ticket\*(R". When the client wishes to resume it sends the encrypted data back to the server. The server uses its key to decrypt the data and resume the session. In this way the server can operate statelessly - no session information needs to be cached locally. .Sp The TLSv1.3 protocol only supports tickets and does not directly support session ids. However, OpenSSL allows two modes of ticket operation in TLSv1.3: stateful and stateless. Stateless tickets work the same way as in TLSv1.2 and below. Stateful tickets mimic the session id behaviour available in TLSv1.2 and below. The session information is cached on the server and the session id is wrapped up in a ticket and sent back to the client. When the client wishes to resume, it presents a ticket in the same way as for stateless tickets. The server can then extract the session id from the ticket and retrieve the session information from its cache. .Sp By default OpenSSL will use stateless tickets. The \s-1SSL_OP_NO_TICKET\s0 option will cause stateless tickets to not be issued. In TLSv1.2 and below this means no ticket gets sent to the client at all. In TLSv1.3 a stateful ticket will be sent. This is a server-side option only. .Sp In TLSv1.3 it is possible to suppress all tickets (stateful and stateless) from being sent by calling SSL_CTX_set_num_tickets\|(3) or \fBSSL_set_num_tickets\|(3). Item "SSL_OP_ALLOW_UNSAFE_LEGACY_RENEGOTIATION" Allow legacy insecure renegotiation between OpenSSL and unpatched clients or servers. See the \s-1SECURE RENEGOTIATION\s0 section for more details. Item "SSL_OP_LEGACY_SERVER_CONNECT" Allow legacy insecure renegotiation between OpenSSL and unpatched servers \fBonly: this option is currently set by default. See the \fB\s-1SECURE RENEGOTIATION\s0 section for more details. Item "SSL_OP_NO_ENCRYPT_THEN_MAC" Normally clients and servers will transparently attempt to negotiate the \s-1RFC7366\s0 Encrypt-then-MAC option on \s-1TLS\s0 and \s-1DTLS\s0 connection. .Sp If this option is set, Encrypt-then-MAC is disabled. Clients will not propose, and servers will not accept the extension. Item "SSL_OP_NO_RENEGOTIATION" Disable all renegotiation in TLSv1.2 and earlier. Do not send HelloRequest messages, and ignore renegotiation requests via ClientHello. Item "SSL_OP_ALLOW_NO_DHE_KEX" In TLSv1.3 allow a non-(ec)dhe based key exchange mode on resumption. This means that there will be no forward secrecy for the resumed session. Item "SSL_OP_PRIORITIZE_CHACHA" When \s-1SSL_OP_CIPHER_SERVER_PREFERENCE\s0 is set, temporarily reprioritize ChaCha20-Poly1305 ciphers to the top of the server cipher list if a ChaCha20-Poly1305 cipher is at the top of the client cipher list. This helps those clients (e.g. mobile) use ChaCha20-Poly1305 if that cipher is anywhere in the server cipher list; but still allows other clients to use \s-1AES\s0 and other ciphers. Requires \s-1SSL_OP_CIPHER_SERVER_PREFERENCE\s0. Item "SSL_OP_ENABLE_MIDDLEBOX_COMPAT" If set then dummy Change Cipher Spec (\s-1CCS\s0) messages are sent in TLSv1.3. This has the effect of making TLSv1.3 look more like TLSv1.2 so that middleboxes that do not understand TLSv1.3 will not drop the connection. Regardless of whether this option is set or not \s-1CCS\s0 messages received from the peer will always be ignored in TLSv1.3. This option is set by default. To switch it off use \fBSSL_clear_options(). A future version of OpenSSL may not set this by default. Item "SSL_OP_NO_ANTI_REPLAY" By default, when a server is configured for early data (i.e., max_early_data > 0), OpenSSL will switch on replay protection. See SSL_read_early_data\|(3) for a description of the replay protection feature. Anti-replay measures are required to comply with the TLSv1.3 specification. Some applications may be able to mitigate the replay risks in other ways and in such cases the built in OpenSSL functionality is not required. Those applications can turn this feature off by setting this option. This is a server-side opton only. It is ignored by clients. Item "SSL_OP_ENABLE_KTLS" Enable the use of kernel \s-1TLS.\s0 In order to benefit from kernel \s-1TLS\s0 OpenSSL must have been compiled with support for it, and it must be supported by the negotiated ciphersuites and extensions. The specific ciphersuites and extensions that are supported may vary by platform and kernel version. .Sp The kernel \s-1TLS\s0 data-path implements the record layer, and the encryption algorithm. The kernel will utilize the best hardware available for encryption. Using the kernel data-path should reduce the memory footprint of OpenSSL because no buffering is required. Also, the throughput should improve because data copy is avoided when user data is encrypted into kernel memory instead of the usual encrypt then copy to kernel. .Sp Kernel \s-1TLS\s0 might not support all the features of OpenSSL. For instance, renegotiation, and setting the maximum fragment size is not possible as of Linux 4.20. .Sp Note that with kernel \s-1TLS\s0 enabled some cryptographic operations are performed by the kernel directly and not via any available OpenSSL Providers. This might be undesirable if, for example, the application requires all cryptographic operations to be performed by the \s-1FIPS\s0 provider.

The following options no longer have any effect but their identifiers are retained for compatibility purposes:

Item "SSL_OP_NETSCAPE_REUSE_CIPHER_CHANGE_BUG"

0

Item "SSL_OP_MICROSOFT_BIG_SSLV3_BUFFER" Item "SSL_OP_SSLEAY_080_CLIENT_DH_BUG" Item "SSL_OP_TLS_D5_BUG" Item "SSL_OP_TLS_BLOCK_PADDING_BUG" Item "SSL_OP_MSIE_SSLV2_RSA_PADDING" Item "SSL_OP_SSLREF2_REUSE_CERT_TYPE_BUG" Item "SSL_OP_MICROSOFT_SESS_ID_BUG" Item "SSL_OP_NETSCAPE_CHALLENGE_BUG" Item "SSL_OP_PKCS1_CHECK_1" Item "SSL_OP_PKCS1_CHECK_2" Item "SSL_OP_SINGLE_DH_USE" Item "SSL_OP_SINGLE_ECDH_USE" Item "SSL_OP_EPHEMERAL_RSA"

Header "SECURE RENEGOTIATION" OpenSSL always attempts to use secure renegotiation as described in \s-1RFC5746.\s0 This counters the prefix attack described in \s-1CVE-2009-3555\s0 and elsewhere.

This attack has far reaching consequences which application writers should be aware of. In the description below an implementation supporting secure renegotiation is referred to as patched. A server not supporting secure renegotiation is referred to as unpatched.

The following sections describe the operations permitted by OpenSSL's secure renegotiation implementation.

Subsection "Patched client and server" Connections and renegotiation are always permitted by OpenSSL implementations. Subsection "Unpatched client and patched OpenSSL server" The initial connection succeeds but client renegotiation is denied by the server with a no_renegotiation warning alert if \s-1TLS\s0 v1.0 is used or a fatal \fBhandshake_failure alert in \s-1SSL\s0 v3.0.

If the patched OpenSSL server attempts to renegotiate a fatal \fBhandshake_failure alert is sent. This is because the server code may be unaware of the unpatched nature of the client.

If the option \s-1SSL_OP_ALLOW_UNSAFE_LEGACY_RENEGOTIATION\s0 is set then renegotiation always succeeds.

Subsection "Patched OpenSSL client and unpatched server." If the option \s-1SSL_OP_LEGACY_SERVER_CONNECT\s0 or \fB\s-1SSL_OP_ALLOW_UNSAFE_LEGACY_RENEGOTIATION\s0 is set then initial connections and renegotiation between patched OpenSSL clients and unpatched servers succeeds. If neither option is set then initial connections to unpatched servers will fail.

The option \s-1SSL_OP_LEGACY_SERVER_CONNECT\s0 is currently set by default even though it has security implications: otherwise it would be impossible to connect to unpatched servers (i.e. all of them initially) and this is clearly not acceptable. Renegotiation is permitted because this does not add any additional security issues: during an attack clients do not see any renegotiations anyway.

As more servers become patched the option \s-1SSL_OP_LEGACY_SERVER_CONNECT\s0 will \fBnot be set by default in a future version of OpenSSL.

OpenSSL client applications wishing to ensure they can connect to unpatched servers should always set \s-1SSL_OP_LEGACY_SERVER_CONNECT\s0

OpenSSL client applications that want to ensure they can not connect to unpatched servers (and thus avoid any security issues) should always clear \fB\s-1SSL_OP_LEGACY_SERVER_CONNECT\s0 using SSL_CTX_clear_options() or \fBSSL_clear_options().

The difference between the \s-1SSL_OP_LEGACY_SERVER_CONNECT\s0 and \fB\s-1SSL_OP_ALLOW_UNSAFE_LEGACY_RENEGOTIATION\s0 options is that \fB\s-1SSL_OP_LEGACY_SERVER_CONNECT\s0 enables initial connections and secure renegotiation between OpenSSL clients and unpatched servers only, while \fB\s-1SSL_OP_ALLOW_UNSAFE_LEGACY_RENEGOTIATION\s0 allows initial connections and renegotiation between OpenSSL and unpatched clients or servers.

Header "RETURN VALUES" \fBSSL_CTX_set_options() and SSL_set_options() return the new options bit mask after adding options.

\fBSSL_CTX_clear_options() and SSL_clear_options() return the new options bit mask after clearing options.

\fBSSL_CTX_get_options() and SSL_get_options() return the current bit mask.

\fBSSL_get_secure_renegotiation_support() returns 1 is the peer supports secure renegotiation and 0 if it does not.

Header "SEE ALSO" \fBssl\|(7), SSL_new\|(3), SSL_clear\|(3), \fBSSL_CTX_set_tmp_dh_callback\|(3), \fBSSL_CTX_set_min_proto_version\|(3), \fBdhparam\|(1) Header "HISTORY" The attempt to always try to use secure renegotiation was added in OpenSSL 0.9.8m.

The \s-1SSL_OP_PRIORITIZE_CHACHA\s0 and \s-1SSL_OP_NO_RENEGOTIATION\s0 options were added in OpenSSL 1.1.1.

Header "COPYRIGHT" Copyright 2001-2020 The OpenSSL Project Authors. All Rights Reserved.

Licensed under the OpenSSL license (the \*(L"License\*(R"). You may not use this file except in compliance with the License. You can obtain a copy in the file \s-1LICENSE\s0 in the source distribution or at <https://www.openssl.org/source/license.html>.