SSL_CTX_SET_MODE(3SSL)

πŸ’– SSL_CTX_SET_MODE πŸ’– (OpenSSL manual, section 3SSL β€” yes bestie we're in the 3SSL girlies)

okay so. this page is about the whole lil' family of functions that let you peek at and poke the mode bit-mask on an SSL engine: SSL_CTX_set_mode, SSL_CTX_clear_mode, SSL_set_mode, SSL_clear_mode, SSL_CTX_get_mode, SSL_get_mode. manipulate SSL engine mode. that's the whole gig. it's giving ✨toggles✨.


🌸 SYNOPSIS 🌸

#include <openssl/ssl.h>

long SSL_CTX_set_mode(SSL_CTX *ctx, long mode);
long SSL_CTX_clear_mode(SSL_CTX *ctx, long mode);
long SSL_set_mode(SSL *ssl, long mode);
long SSL_clear_mode(SSL *ssl, long mode);

long SSL_CTX_get_mode(SSL_CTX *ctx);
long SSL_get_mode(SSL *ssl);

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the tea. SSL_CTX_set_mode() adds the mode you pass in via the bit-mask in mode to ctx. and bestie, options that were already set before? not cleared. we do not erase, we only add. πŸ’…

SSL_CTX_clear_mode() does the opposite β€” it removes the mode set via bit-mask in mode from ctx.

SSL_set_mode() adds the mode set via bit-mask in mode to ssl. same deal, options already set before are not cleared. SSL_clear_mode() removes the mode set via bit-mask in mode from ssl.

SSL_CTX_get_mode() returns the mode set for ctx. πŸ“–

SSL_get_mode() returns the mode set for ssl.


✨ NOTES ✨

here's the mode menu, bestie, every single one, no skips:

  • SSL_MODE_ENABLE_PARTIAL_WRITE β€” lets SSL_write_ex(..., n, &r) come back with 0 < r < n, i.e. it reports success even when only a single record got written. same energy for SSL_write(). when this is not set (that's the default), SSL_write_ex() or SSL_write() only report success once the complete chunk was written. once SSL_write_ex() or SSL_write() returns successful, r bytes have been written and the next call to SSL_write_ex() or SSL_write() must only send the n-r bytes left β€” imitating the behaviour of write().
heads up: this mode cannot be enabled while you're in the middle of an incomplete write operation. mid-write is not the moment, bestie. 🫠
  • SSL_MODE_ACCEPT_MOVING_WRITE_BUFFER β€” makes it possible to retry SSL_write_ex() or SSL_write() with a changed buffer location (the buffer contents must stay the same tho!). this is not the default, and the reason is to avoid the misconception that nonblocking SSL_write() behaves like nonblocking write(). 🚫
  • SSL_MODE_AUTO_RETRY β€” during normal operations, non-application data records might need to be sent or received that the application is not aware of. if a non-application data record was processed, SSL_read_ex(3) and SSL_read(3) can return with a failure and indicate the need to retry with SSL_ERROR_WANT_READ. if such a non-application data record was processed, the flag SSL_MODE_AUTO_RETRY causes it to try to process the next record instead of returning. 🎒

in a nonblocking environment, applications must be prepared to handle incomplete read/write operations. setting SSL_MODE_AUTO_RETRY for a nonblocking BIO will process non-application data records until either no more data is available or an application data record has been processed.

in a blocking environment, applications are not always prepared to deal with the functions returning intermediate reports such as retry requests, and setting the SSL_MODE_AUTO_RETRY flag will cause the functions to only return after successfully processing an application data record or a failure.

turning off SSL_MODE_AUTO_RETRY can be useful with blocking BIOs in case they are used in combination with something like select() or poll(). otherwise the call to SSL_read() or SSL_read_ex() might hang when a non-application record was sent and no application data was sent. 😭

  • SSL_MODE_RELEASE_BUFFERS β€” when we no longer need a read buffer or a write buffer for a given SSL, then release the memory we were using to hold it. using this flag can save around 34k per idle SSL connection. that's a glow-up for your RAM, fr fr. this flag has no effect on SSL v2 connections, or on DTLS connections.
  • SSL_MODE_SEND_FALLBACK_SCSV β€” send TLS_FALLBACK_SCSV in the ClientHello. to be set only by applications that reconnect with a downgraded protocol version; see draft-ietf-tls-downgrade-scsv-00 for details.
🚨 DO NOT ENABLE THIS if your application attempts a normal handshake. only use this in explicit fallback retries, following the guidance in draft-ietf-tls-downgrade-scsv-00. i am literally begging you.
  • SSL_MODE_ASYNC β€” enable asynchronous processing. TLS I/O operations may indicate a retry with SSL_ERROR_WANT_ASYNC with this mode set if an asynchronous capable provider is used to perform cryptographic operations. see SSL_get_error(3). ⚑
  • SSL_MODE_DTLS_SCTP_LABEL_LENGTH_BUG β€” older versions of OpenSSL had a bug in the computation of the label length used for computing the endpoint-pair shared secret. the bug was that the terminating zero was included in the length of the label. setting this option enables this behaviour to allow interoperability with such broken implementations. please note that setting this option breaks interoperability with correct implementations. this option only applies to DTLS over SCTP. πŸ’€ (legacy bug-compat mode, iconic behaviour honestly)

and the grand finale: all modes are off by default except for SSL_MODE_AUTO_RETRY, which is on by default since 1.1.1. πŸ‘‘


πŸŽ€ RETURN VALUES πŸŽ€

  • SSL_CTX_set_mode() and SSL_set_mode() return the new mode bit-mask after adding mode.
  • SSL_CTX_get_mode() and SSL_get_mode() return the current bit-mask.

πŸ‘‘ SEE ALSO πŸ‘‘

ssl(7), SSL_read_ex(3), SSL_read(3), SSL_write_ex(3) or SSL_write(3), SSL_get_error(3)

go read those too, bestie, they're the friends of this page. 🫢


🌈 HISTORY 🌈

SSL_MODE_ASYNC was added in OpenSSL 1.1.0. a legend was born. ⭐


Copyright 2001-2023 The OpenSSL Project Authors. All Rights Reserved.

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>.


and that's the whole page, bestie!! go forth and mode responsibly πŸ’–βœ¨

this has been OpenSSL 4.0.3, dated 2026-09-29, from the SSL_CTX_SET_MODE(3SSL) era β€” no cap, periodt. πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from