stunnel(8)

📦

version 5.77 · 5 versions

🦋 stunnel(8) — TLS offloading and load-balancing proxy 🦋

Okay so bestie, welcome to the stunnel(8) manual page. This is the stunnel4 TLS Proxy situation, and we're about to make TLS offloading and load-balancing make sense. No cap. ✨

✨ NAME ✨

stunnel — TLS offloading and load-balancing proxy

🌸 SYNOPSIS 🌸

Unix besties:

Unix:
    stunnel [FILE] | -fd N | -help | -version | -sockets | -options

WIN32:
    stunnel [ [ -install | -uninstall | -start | -stop |
        -reload | -reopen | -exit ] [-quiet] [FILE] ] |
        -help | -version | -sockets | -options

💖 DESCRIPTION 💖

Okay so stunnel is literally designed to work as a TLS encryption wrapper between remote clients and local (inetd-startable) or remote servers. The whole concept? You have non-TLS aware daemons running on your system, and you can easily set them up to communicate with clients over secure TLS channels. Iconic behavior, honestly. 💅

stunnel can be used to add TLS functionality to commonly used Inetd daemons like POP-2, POP-3, and IMAP servers, to standalone daemons like NNTP, SMTP and HTTP, and in tunneling PPP over network sockets without changes to the source code. Ate. 🔥

This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)

👑 OPTIONS 👑

FILE — Use specified configuration file.
-fd N (Unix only) — Read the config file from specified file descriptor.
-help — Print stunnel help menu.
-version — Print stunnel version and compile time defaults.
-sockets — Print default socket options.
-options — Print supported TLS options.
-install (Windows NT and later only) — Install NT Service.
-uninstall (Windows NT and later only) — Uninstall NT Service.
-start (Windows NT and later only) — Start NT Service.
-stop (Windows NT and later only) — Stop NT Service.
-reload (Windows NT and later only) — Reload the configuration file of the running NT Service.
-reopen (Windows NT and later only) — Reopen the log file of the running NT Service.
-exit (Win32 only) — Exit an already started stunnel.
-quiet (Win32 only) — Don't display any message boxes.

🌈 CONFIGURATION FILE 🌈

Each line of the configuration file can be either:

An empty line (ignored).
A comment starting with ; (ignored).
An option_name = option_value pair.
[service_name] indicating a start of a service definition.

An address parameter of an option may be either:

A port number.
A colon-separated pair of IP address (either IPv4, IPv6, or domain name) and port number.
A Unix socket path (Unix only).

💅 GLOBAL OPTIONS 💅

chroot = DIRECTORY (Unix only) — directory to chroot stunnel process.
- chroot keeps stunnel in a chrooted jail. CApath, CRLpath, pid and exec are located inside the jail and the patches have to be relative to the directory specified with chroot.
- Several functions of the operating system also need their files to be located within the chroot jail, e.g.:
  - Delayed resolver typically needs /etc/nsswitch.conf and /etc/resolv.conf.
  - Local time in log files needs /etc/timezone.
  - Some other functions may need devices, e.g. /dev/zero or /dev/null.
compression = deflate | zlib — select data compression algorithm.
- default: no compression
- Deflate is the standard compression method as described in RFC 1951.
debug = [FACILITY.]LEVEL — debugging level.
- Level is one of the syslog level names or numbers emerg (0), alert (1), crit (2), err (3), warning (4), notice (5), info (6), or debug (7). All logs for the specified level and all levels numerically less than it will be shown.
- The debug = debug (or the equivalent <debug = 7>) level produces for the most verbose log output. This logging level is only meant to be understood by stunnel developers, and not by users. Please either use the debug level when requested to do so by an stunnel developer, or when you intend to get confused.
- The default logging level is notice (5).
- The syslog 'daemon' facility will be used unless a facility name is supplied. (Facilities are not supported on Win32.)
- Case is ignored for both facilities and levels.
EGD = EGD_PATH (Unix only) — path to Entropy Gathering Daemon socket.
- Entropy Gathering Daemon socket to use to feed the OpenSSL random number generator.
engine = auto | ENGINE_ID — select hardware or software cryptographic engine.
- default: software-only cryptography
- See Examples section for an engine configuration to use the certificate and the corresponding private key from a cryptographic device.
engineCtrl = COMMAND[:PARAMETER] — control hardware engine.
engineDefault = TASK_LIST — set OpenSSL tasks delegated to the current engine.
- The parameter specifies a comma-separated list of task to be delegated to the current engine.
- The following tasks may be available, if supported by the engine: ALL, RSA, DSA, ECDH, ECDSA, DH, RAND, CIPHERS, DIGESTS, PKEY, PKEY_CRYPTO, PKEY_ASN1.
fips = yes | no — enable or disable FIPS 140-2 mode.
- This option allows you to disable entering FIPS mode if stunnel was compiled with FIPS 140-2 support.
- default: no (since version 5.00)
foreground = yes | quiet | no (Unix only) — foreground mode.
- Stay in foreground (don't fork).
- With the yes parameter it also logs to stderr in addition to the destinations specified with syslog and output.
- default: background in daemon mode
iconActive = ICON_FILE (GUI only) — GUI icon to be displayed when there are established connections.
- On Windows platform the parameter should be an .ico file containing a 16x16 pixel image.
iconError = ICON_FILE (GUI only) — GUI icon to be displayed when no valid configuration is loaded.
- On Windows platform the parameter should be an .ico file containing a 16x16 pixel image.
iconIdle = ICON_FILE (GUI only) — GUI icon to be displayed when there are no established connections.
- On Windows platform the parameter should be an .ico file containing a 16x16 pixel image.
log = append | overwrite — log file handling.
- This option allows you to choose whether the log file (specified with the output option) is appended or overwritten when opened or re-opened.
- default: append
output = FILE — append log messages to a file.
- /dev/stdout device can be used to send log messages to the standard output (for example to log them with daemontools splogger).
pid = FILE (Unix only) — pid file location.
- If the argument is empty, then no pid file will be created.
- pid path is relative to the chroot directory if specified.
provider = PROVIDER_ID — Specifies the identifier of the provider to be used. PROVIDER_ID is a unique identifier referring to a specific cryptographic service provider.
- This option requires OpenSSL 3.0 or later.
providerParameter = PROVIDER_ID:PARAMETER=VALUE — Sets a specific parameter for the given provider. PROVIDER_ID identifies the provider, PARAMETER is the parameter name, and VALUE is its value. This option allows customization of the selected cryptographic service provider's configuration.
- This option requires OpenSSL 3.5 or later.
RNDbytes = BYTES — bytes to read from random seed files.
RNDfile = FILE — path to file with random seed data.
- The OpenSSL library will use data from this file first to seed the random number generator.
RNDoverwrite = yes | no — overwrite the random seed files with new random data.
- default: yes
service = SERVICE (Unix only) — stunnel service name.
- The specified service name is used for syslog and as the inetd mode service name for TCP Wrappers. While this option can technically be specified in the service sections, it is only useful in global options.
- default: stunnel
setEnv = VAR_NAME=VALUE — Change or add an environment variable for child processes. If VAR_NAME already exists, its value will be updated; otherwise, a new variable will be created. This modification applies only to spawned child processes and does not affect the current environment.
syslog = yes | no (Unix only) — enable logging via syslog.
- default: yes
taskbar = yes | no (WIN32 only) — enable the taskbar icon.
- default: yes

🎀 SERVICE-LEVEL OPTIONS 🎀

Each configuration section begins with a service name in square brackets. The service name is used for libwrap (TCP Wrappers) access control and lets you distinguish stunnel services in your log files.

Note that if you wish to run stunnel in inetd mode (where it is provided a network socket by a server such as inetd, xinetd, or tcpserver) then you should read the section entitled INETD MODE below.

accept = [HOST:]PORT — accept connections on specified address.
- If no host specified, defaults to all IPv4 addresses for the local host.
- To listen on all IPv6 addresses use:

accept = :::PORT

CAengine = ENGINE-SPECIFIC_CA_CERTIFICATE_IDENTIFIER — load a trusted CA certificate from an engine.
- The loaded CA certificates will be used with the verifyChain and verifyPeer options.
- Multiple CAengine options are allowed in a single service section.
- Currently supported engines: pkcs11, cng.
CApath = CA_DIRECTORY — load trusted CA certificates from a directory.
- The loaded CA certificates will be used with the verifyChain and verifyPeer options. Note that the certificates in this directory should be named XXXXXXXX.0 where XXXXXXXX is the hash value of the DER encoded subject of the cert.
- This parameter can also be used to provide the root CA certificate needed to validate OCSP stapling in server mode.
- The hash algorithm has been changed in OpenSSL 1.0.0. It is required to c_rehash the directory on upgrade from OpenSSL 0.x.x to OpenSSL 1.x.x or later.
- CApath path is relative to the chroot directory if specified.
CAfile = CA_FILE — load trusted CA certificates from a file.
- The loaded CA certificates will be used with the verifyChain and verifyPeer options.
- This parameter can also be used to provide the root CA certificate needed to validate OCSP stapling in server mode.
CAstore = URI_CA — load trusted CA certificates from a resource specified by a URI.
- This option allows loading CA certificates from an external source supported by the OSSL_STORE framework, such as a PKCS#11 module (e.g., hardware token), the system certificate store, or a remote resource.

This option can be used independently of CAfile and CAdir, and similarly provides certificates used by verifyChain or verifyPeer, as well as for validating OCSP stapling in server mode. 💅

This option requires OpenSSL 3.0 or later. (bestie the version gates are everywhere, iykyk)

cert = CERT_FILE | URI — certificate chain file name 🎀

The parameter specifies the file containing certificates used by stunnel to authenticate itself against the remote client or server. The file should contain the whole certificate chain starting from the actual server/client certificate, and ending with the self-signed root CA certificate. The file must be either in PEM or P12 format.

A certificate chain is required in server mode, and optional in client mode. 👑

The cert option may be specified multiple times. The first certificate encountered is used as the server or client certificate, while any subsequent certificates are treated as intermediate chain elements. This functionality requires OpenSSL version 1.0.2 or later.

This parameter is also used as the certificate identifier (PKCS#11 URI) when a hardware engine or provider is enabled. 🔥

Note: The provider requires OpenSSL 3.0 or later

checkEmail = EMAIL — verify the email address of the end-entity (leaf) peer certificate subject 📧

Certificates are accepted if no subject checks were specified, or the email address of the end-entity (leaf) peer certificate matches any of the email addresses specified with checkEmail.

Multiple checkEmail options are allowed in a single service section. ✨

This option requires OpenSSL 1.0.2 or later.

checkHost = HOST — verify the host of the end-entity (leaf) peer certificate subject 🦋

Certificates are accepted if no subject checks were specified, or the host name of the end-entity (leaf) peer certificate matches any of the hosts specified with checkHost.

Multiple checkHost options are allowed in a single service section. ✨

This option requires OpenSSL 1.0.2 or later.

checkIP = IP — verify the IP address of the end-entity (leaf) peer certificate subject 🌐

Certificates are accepted if no subject checks were specified, or the IP address of the end-entity (leaf) peer certificate matches any of the IP addresses specified with checkIP.

Multiple checkIP options are allowed in a single service section. ✨

This option requires OpenSSL 1.0.2 or later.

ciphers = CIPHER_LIST — select permitted TLS ciphers (TLSv1.2 and below) 🔐

This option does not impact TLSv1.3 ciphersuites. (they got their own whole option, be patient)

A colon-delimited list of the ciphers to allow in the TLS connection, for example DES-CBC3-SHA:IDEA-CBC-MD5.

ciphersuites = CIPHERSUITES_LIST — select permitted TLSv1.3 ciphersuites ✨

A colon-delimited list of TLSv1.3 ciphersuites names in order of preference.

The ciphersuites option ignores unknown ciphers when compiled with OpenSSL 3.0 or later.

This option requires OpenSSL 1.1.1 or later.

default:

TLS_CHACHA20_POLY1305_SHA256:TLS_AES_256_GCM_SHA384:TLS_AES_128_GCM_SHA256

client = yes | no — client mode (remote service uses TLS) 🧚

default: no (server mode)

config = COMMAND[:PARAMETER] — OpenSSL configuration command 🛠️

The OpenSSL configuration command is executed with the specified parameter. This allows any configuration commands to be invoked from the stunnel configuration file. Supported commands are described on the SSL_CONF_cmd(3ssl) manual page.

Several config lines can be used to specify multiple configuration commands.

Use curves option instead of enabling config = Curves:list_curves to support elliptic curves. (not me catching you trying the sneaky way 🙈)

This option requires OpenSSL 1.0.2 or later.

connect = [HOST:]PORT — connect to a remote address 🔌

If no host is specified, the host defaults to localhost.

Multiple connect options are allowed in a single service section. If host resolves to multiple addresses and/or if multiple connect options are specified, then the remote address is chosen using a round-robin algorithm.

CRLpath = DIRECTORY — Certificate Revocation Lists directory 🚫

This is the directory in which stunnel will look for CRLs when using the verifyChain and verifyPeer options. Note that the CRLs in this directory should be named XXXXXXXX.r0 where XXXXXXXX is the hash value of the CRL.

The hash algorithm has been changed in OpenSSL 1.0.0. It is required to c_rehash the directory on upgrade from OpenSSL 0.x.x to OpenSSL 1.x.x. ⚠️

CRLpath path is relative to the chroot directory if specified.

CRLfile = CRL_FILE — Certificate Revocation Lists file 📄

This file contains multiple CRLs, used with the verifyChain and verifyPeer options.

curves = list — ECDH curves separated with ':' 🌀

Note: This option is supported for server mode sockets only.

Only a single curve name is allowed for OpenSSL older than 1.1.1.

To get a list of supported curves use:

openssl ecparam -list_curves

default:

X25519:P-256:X448:P-521:P-384 (OpenSSL 1.1.1 or later)

prime256v1 (OpenSSL older than 1.1.1)

logId = TYPE — connection identifier type 🏷️

This identifier allows you to distinguish log entries generated for each of the connections.

Currently supported types:

sequential — The numeric sequential identifier is only unique within a single instance of stunnel, but very compact. It is most useful for manual log analysis.
unique — This alphanumeric identifier is globally unique, but longer than the sequential number. It is most useful for automated log analysis.
thread — The operating system thread identifier is neither unique (even within a single instance of stunnel) nor short. It is most useful for debugging software or configuration issues.
process — The operating system process identifier (PID) may be useful in the inetd mode.

default: sequential

debug = LEVEL — debugging level 🐛

Level is a one of the syslog level names or numbers emerg (0), alert (1), crit (2), err (3), warning (4), notice (5), info (6), or debug (7). All logs for the specified level and all levels numerically less than it will be shown. The default is notice (5).

While the debug = debug or debug = 7 level generates the most verbose output, it is only intended to be used by stunnel developers. Please only use this value if you are a developer, or you intend to send your logs to our technical support. Otherwise, the generated logs will be confusing. 💀

delay = yes | no — delay DNS lookup for the connect option ⏳

This option is useful for dynamic DNS, or when DNS is not available during stunnel startup (road warrior VPN, dial-up configurations).

Delayed resolver mode is automatically engaged when stunnel fails to resolve on startup any of the connect targets for a service.

Delayed resolver inflicts failover = prio. (it just does, no arguing 🌸)

default: no

engineId = ENGINE_ID — select engine ID for the service 🔧
engineNum = ENGINE_NUMBER — select engine number for the service 🔢

The engines are numbered starting from 1.

exec = EXECUTABLE_PATH — execute a local inetd-type program 🏃

exec path is relative to the chroot directory if specified.

The following environmental variables are set on Unix platforms: REMOTE_HOST, REMOTE_PORT, SSL_CLIENT_DN, SSL_CLIENT_I_DN.

execArgs = $0 $1 $2 ... — arguments for exec including the program name ($0) 📝

Quoting is currently not supported. Arguments are separated with an arbitrary amount of whitespace.

failover = rr | prio — Failover strategy for multiple "connect" targets. 🔁
- rr — round robin - fair load distribution
- prio — priority - use the order specified in config file

default: prio

ident = USERNAME — use IDENT (RFC 1413) username checking 🪪
include = DIRECTORY — include all configuration file parts located in DIRECTORY 📂

The files are included in the ascending alphabetical order of their names. The recommended filename convention is

for global options:

00-global.conf

for local service-level options:

01-service.conf

02-service.conf

key = KEY_FILE | URI — private key for the certificate specified with cert option 🔑

A private key is needed to authenticate the certificate owner. Since this file should be kept secret it should only be readable by its owner. On Unix systems you can use the following command:

chmod 600 keyfile

This parameter is also used as the private key identifier (PKCS#11 URI) when a hardware engine or provider is enabled.

Note: The provider requires OpenSSL 3.0 or later

default: the value of the cert option

libwrap = yes | no — Enable or disable the use of /etc/hosts.allow and /etc/hosts.deny. 🚧

default: no (since version 5.00)

local = HOST — By default, the IP address of the outgoing interface is used as the source for remote connections. Use this option to bind a static local IP address instead. 📍
OCSP = URL — select OCSP responder for the end-entity (leaf) peer certificate verification 🩺
OCSPaia = yes | no — validate certificates with their AIA OCSP responders 🔎

This option enables stunnel to validate certificates with the list of OCSP responder URLs retrieved from their AIA (Authority Information Access) extension.

OCSPflag = OCSP_FLAG — specify OCSP responder flag 🚩

Several OCSPflag can be used to specify multiple flags.

currently supported flags: NOCERTS, NOINTERN, NOSIGS, NOCHAIN, NOVERIFY, NOEXPLICIT, NOCASIGN, NODELEGATED, NOCHECKS, TRUSTOTHER, RESPID_KEY, NOTIME

OCSPnonce = yes | no — send and verify the OCSP nonce extension 🎲

This option protects the OCSP protocol against replay attacks. Due to its computational overhead, the nonce extension is usually only supported on internal (e.g. corporate) responders, and not on public OCSP responders.

OCSPrequire = yes | no — require a conclusive OCSP response ✅

Disable this option to allow a connection even though no conclusive OCSP response was retrieved from stapling and a direct request to the OCSP responder.

default: yes

options = SSL_OPTIONS — OpenSSL library options ⚙️

Okay so bestie, that parameter? It’s literally the OpenSSL option name from the SSL_CTX_set_options(3ssl) manual, but you have to drop the SSL_OP_ prefix. 💅 And stunnel -options will spill the tea on which options are allowed in the exact combo of stunnel and the OpenSSL library you built it with. ✨

You can stack several options lines to set multiple options, no cap. And if you put a dash (-) in front of an option name, it disables that option. 🙈

For example, for compatibility with the erroneous Eudora TLS implementation, you can use:

options = DONT_INSERT_EMPTY_FRAGMENTS

default:

options = NO_SSLv2
options = NO_SSLv3

When you’re compiled with OpenSSL 1.1.0 or later, use sslVersionMax or sslVersionMin instead of disabling specific TLS protocol versions. Periodt. 🎀

`protocol = PROTO`

application protocol to negotiate TLS — this one enables initial, protocol-specific negotiation of the TLS encryption. 🦋

⚠️ The protocol option should not be used with TLS encryption on a separate port.

Currently supported protocols:

cifs — Proprietary (undocumented) extension of CIFS protocol implemented in Samba. Support for this extension was dropped in Samba 3.0.0. 💀
capwin — http://www.capwin.org/ application support 🌈
capwinctrl — http://www.capwin.org/ application support
- This protocol is only supported in client mode. 🫶
connect — Based on RFC 2817 - Upgrading to TLS Within HTTP/1.1, section 5.2 - Requesting a Tunnel with CONNECT
- This protocol is only supported in client mode. 🫶
imap — Based on RFC 2595 - Using TLS with IMAP, POP3 and ACAP
ldap — Based on RFC 2830 - Lightweight Directory Access Protocol (v3): Extension for Transport Layer Security
nntp — Based on RFC 4642 - Using Transport Layer Security (TLS) with Network News Transfer Protocol (NNTP)
- This protocol is only supported in client mode. 🫶
pgsql — Based on http://www.postgresql.org/docs/8.3/static/protocol-flow.html#AEN73982
pop3 — Based on RFC 2449 - POP3 Extension Mechanism
proxy — Passing of the original client IP address with HAProxy PROXY protocol version 1 https://www.haproxy.org/download/1.8/doc/proxy-protocol.txt
smtp — Based on RFC 2487 - SMTP Service Extension for Secure SMTP over TLS
socks — SOCKS versions 4, 4a, and 5 are supported. The SOCKS protocol itself is encapsulated within TLS encryption layer to protect the final destination address. 🔥
- http://www.openssh.com/txt/socks4.protocol
- http://www.openssh.com/txt/socks4a.protocol
- The BIND command of the SOCKS protocol is not supported. The USERID parameter is ignored. 🙅
- See Examples section for sample configuration files for VPN based on SOCKS encryption. 👑

`protocolAuthentication = AUTHENTICATION`

authentication type for the protocol negotiations 🔐

Currently, this option is only supported in the client-side connect and smtp protocols.

Supported authentication types for the connect protocol are basic or ntlm. The default connect authentication type is basic.

Supported authentication types for the smtp protocol are plain or login. The default smtp authentication type is plain.

`protocolDomain = DOMAIN`

domain for the protocol negotiations 🌐

Currently, this option is only supported in the client-side connect protocol.

`protocolHeader = HEADER`

header for the protocol negotiations 📨

Currently, this option is only supported in the client-side connect protocol.

`protocolHost = ADDRESS`

host address for the protocol negotiations 🏠

For the connect protocol negotiations, protocolHost specifies HOST:PORT of the final TLS server to be connected to by the proxy. The proxy server directly connected by stunnel must be specified with the connect option.

For the smtp protocol negotiations, protocolHost controls the client SMTP HELO/EHLO value.

`protocolPassword = PASSWORD`

password for the protocol negotiations 🔑

Currently, this option is only supported in the client-side connect and smtp protocols.

`protocolUsername = USERNAME`

username for the protocol negotiations 🪪

Currently, this option is only supported in the client-side connect and smtp protocols.

`PSKidentity = IDENTITY`

PSK identity for the PSK client 🆔

PSKidentity can be used on stunnel clients to select the PSK identity used for authentication. This option is ignored in server sections.

default: the first identity specified in the PSKsecrets file.

`PSKsecrets = FILE`

file with PSK identities and corresponding keys 🗝️

Each line of the file in the following format:

IDENTITY:KEY

Hexadecimal keys are automatically converted to binary form. Keys are required to be at least 16 bytes long, which implies at least 32 characters for hexadecimal keys. The file should neither be world-readable nor world-writable. 🚫

`pty = yes | no (Unix only)`

allocate a pseudoterminal for exec option 🖥️

`redirect = [HOST:]PORT`

redirect TLS client connections on certificate-based authentication failures ↩️

This option only works in server mode. Some protocol negotiations are also incompatible with the redirect option.

`renegotiation = yes | no`

support TLS renegotiation 🔄

Applications of the TLS renegotiation include some authentication scenarios, or re-keying long lasting connections.

On the other hand this feature can facilitate a trivial CPU-exhaustion DoS attack:

http://vincent.bernat.im/en/blog/2011-ssl-dos-mitigation.html

Please note that disabling TLS renegotiation does not fully mitigate this issue.

default: yes (if supported by OpenSSL)

`reset = yes | no`

attempt to use the TCP RST flag to indicate an error 🚩

This option is not supported on some platforms.

default: yes

`retry = yes | no | DELAY`

reconnect a connect+exec section after it was disconnected 🔁

The DELAY value specifies the number of milliseconds before retrying. retry = yes has the same effect as retry = 1000.

default: no

`securityLevel = LEVEL`

set the security level 🔒

The meaning of each level is described below:

level 0 — Everything is permitted. 🥳
level 1 — The security level corresponds to a minimum of 80 bits of security. Any parameters offering below 80 bits of security are excluded. As a result RSA, DSA and DH keys shorter than 1024 bits and ECC keys shorter than 160 bits are prohibited. All export cipher suites are prohibited since they all offer less than 80 bits of security. SSL version 2 is prohibited. Any cipher suite using MD5 for the MAC is also prohibited. Additionally, SSLv3, TLS 1.0, TLS 1.1 are all disabled for OpenSSL 3.0 and later.
level 2 — Security level set to 112 bits of security. As a result RSA, DSA and DH keys shorter than 2048 bits and ECC keys shorter than 224 bits are prohibited. In addition to the level 1 exclusions any cipher suite using RC4 is also prohibited. Compression is disabled. SSL version 3 is also not allowed for OpenSSL older than 3.0.
level 3 — Security level set to 128 bits of security. As a result RSA, DSA and DH keys shorter than 3072 bits and ECC keys shorter than 256 bits are prohibited. In addition to the level 2 exclusions cipher suites not offering forward secrecy are prohibited. Session tickets are disabled. TLS versions below 1.1 are not permitted for OpenSSL older than 3.0.
level 4 — Security level set to 192 bits of security. As a result RSA, DSA and DH keys shorter than 7680 bits and ECC keys shorter than 384 bits are prohibited. Cipher suites using SHA1 for the MAC are prohibited. TLS versions below 1.2 are not permitted for OpenSSL older than 3.0.
level 5 — Security level set to 256 bits of security. As a result RSA, DSA and DH keys shorter than 15360 bits and ECC keys shorter than 512 bits are prohibited.

default: 2

The securityLevel option is only available when compiled with OpenSSL 1.1.0 and later.

`requireCert = yes | no`

require a client certificate for verifyChain or verifyPeer 📜

With requireCert set to no, the stunnel server accepts client connections that did not present a certificate.

Both verifyChain = yes and verifyPeer = yes imply requireCert = yes.

default: no

`setgid = GROUP (Unix only)`

Unix group id 👥

As a global option: setgid() to the specified group in daemon mode and clear all other groups.

As a service-level option: set the group of the Unix socket specified with accept.

`setuid = USER (Unix only)`

Unix user id 👤

As a global option: setuid() to the specified user in daemon mode.

As a service-level option: set the owner of the Unix socket specified with accept.

`sessionCacheSize = NUM_ENTRIES`

session cache size 🗃️

sessionCacheSize specifies the maximum number of the internal session cache entries.

The value of 0 can be used for unlimited size. It is not recommended for production use due to the risk of a memory exhaustion DoS attack. 😵

`sessionCacheTimeout = TIMEOUT`

session cache timeout ⏳

This is the number of seconds to keep cached TLS sessions.

`sessionResume = yes | no`

allow or disallow session resumption 🔄

default: yes

`sessiond = HOST:PORT`

address of sessiond TLS cache server 🗄️

`sni = SERVICE_NAME:SERVER_NAME_PATTERN (server mode)`

Use the service as a secondary service (a name-based virtual server) for Server Name Indication TLS extension (RFC 3546). 🌟

SERVICE_NAME specifies the primary service that accepts client connections with the accept option. SERVER_NAME_PATTERN specifies the host name to be redirected. The pattern may start with the '*' character, e.g. '*.example.com'. Multiple secondary services are normally specified for a single primary service. The sni option can also be specified more than once within a single secondary service.

Also? Real talk, bestie: this service, same as the primary service, cannot be configured in client mode. Not a vibe, just facts. 💅

The connect option of the secondary service is ignored when the protocol option is specified, because protocol connects to the remote host before the TLS handshake. So it's giving "we already connected, bestie" energy.

Libwrap checks (Unix only) are performed twice: with the primary service name after the TCP connection is accepted, and with the secondary service name during the TLS handshake. Two vibe checks, one connection. ✨

The sni option is only available when compiled with OpenSSL 1.0.0 and later. So if you're on ancient OpenSSL, sorry babe. 😭

`sni = SERVER_NAME` (client mode) 🎀

Use the parameter as the value of the TLS Server Name Indication (RFC 3546) extension. It's giving "hi, I'm here for this hostname" energy.

Empty SERVER_NAME disables sending the SNI extension. So if you leave it empty, no SNI for you.

The sni option is only available when compiled with OpenSSL 1.0.0 and later. OpenSSL 1.0.0+ girlies only. 💖

`socket = a|l|r:OPTION=VALUE[:VALUE]` 🧦

Set an option on the accept/local/remote socket. a = accept, l = local, r = remote. Got it? Good.

The values for the linger option are l_onof:l_linger. The values for the time are tv_sec:tv_usec. Numbers go brrr.

Examples, bestie:

socket = l:SO_LINGER=1:60
    set one minute timeout for closing local socket
socket = r:SO_OOBINLINE=yes
    place out-of-band data directly into the
    receive data stream for remote sockets
socket = a:SO_REUSEADDR=no
    disable address reuse (enabled by default)
socket = a:SO_BINDTODEVICE=lo
    only accept connections on loopback interface

`sslVersion = SSL_VERSION` 🌈

select the TLS protocol version. Main character energy, but make it cryptographic.

Supported versions: all, SSLv2, SSLv3, TLSv1, TLSv1.1, TLSv1.2, TLSv1.3.

Availability of specific protocols depends on the linked OpenSSL library. Older versions of OpenSSL do not support TLSv1.1, TLSv1.2 and TLSv1.3. Newer versions of OpenSSL do not support SSLv2. So check your OpenSSL, bestie.

Obsolete SSLv2 and SSLv3 are currently disabled by default. We don't do legacy insecure vibes here.

Setting the option

sslVersion = SSL_VERSION

is equivalent to options

sslVersionMax = SSL_VERSION
sslVersionMin = SSL_VERSION

when compiled with OpenSSL 1.1.0 and later. So it's giving "two options in a trench coat" energy.

`sslVersionMax = SSL_VERSION` 🔝

maximum supported protocol versions. It's the ceiling, the limit, the "no higher than this" queen.

Supported versions: all, SSLv3, TLSv1, TLSv1.1, TLSv1.2, TLSv1.3.

all enable protocol versions up to the highest version supported by the linked OpenSSL library. So literally max out.

Availability of specific protocols depends on the linked OpenSSL library. Check it.

The sslVersionMax option is only available when compiled with OpenSSL 1.1.0 and later. Older OpenSSL? Not invited.

default: all

`sslVersionMin = SSL_VERSION` 🔻

minimum supported protocol versions. The floor, the "don't go below this" boundary.

Supported versions: all, SSLv3, TLSv1, TLSv1.1, TLSv1.2, TLSv1.3.

all enable protocol versions down to the lowest version supported by the linked OpenSSL library. So literally bottom out.

Availability of specific protocols depends on the linked OpenSSL library. Again, check it.

The sslVersionMin option is only available when compiled with OpenSSL 1.1.0 and later.

default: TLSv1

`stack = BYTES` (except for FORK model) 🥞

CPU stack size of created threads. Yes, stack size. Not the data structure, the literal memory stack. 💅

Excessive thread stack size increases virtual memory usage. Insufficient thread stack size may cause application crashes. So don't go too big, don't go too small. Goldilocks vibes.

default: 65536 bytes (sufficient for all platforms we tested)

`ticketKeySecret = SECRET` 🎟️

hexadecimal symmetric key used for session ticket confidentiality protection. It's giving "secret key, but make it hexadecimal".

Session tickets defined in RFC 5077 provide an enhanced session resumption capability, where the server-side caching is not required to maintain per session state. No cache, just tickets. Iconic.

Combining ticketKeySecret and ticketMacSecret options allow to resume a negotiated session on other cluster nodes, or to resume a negotiated session after server restart. Cluster-wide resumption? We love to see it.

The key is required to be either 16 or 32 bytes long, which implies exactly 32 or 64 hexadecimal digits. Colons may optionally be used between two-character hexadecimal bytes. So aa:bb:cc is fine, aabbcc is fine.

This option only works in server mode. Client mode? Not today.

The ticketKeySecret option is only available when compiled with OpenSSL 1.0.0 and later.

Disabling NO_TICKET option is required for the ticket support in OpenSSL older than 1.1.1, but note that this option is incompatible with the redirect option. So yeah, pick your battles.

`ticketMacSecret = SECRET` 🔐

hexadecimal symmetric key used for session ticket integrity protection. This one is the MAC, the integrity check, the "is this ticket legit?" vibe.

The key is required to be either 16 or 32 bytes long, which implies exactly 32 or 64 hexadecimal digits. Colons may optionally be used between two-character hexadecimal bytes. Same hex rules, bestie.

This option only works in server mode.

The ticketMacSecret option is only available when compiled with OpenSSL 1.0.0 and later.

`TIMEOUTbusy = SECONDS` ⏳ — time to wait for expected data

`TIMEOUTclose = SECONDS` ⏳ — time to wait for `close_notify` (set to `0` for buggy MSIE)

`TIMEOUTconnect = SECONDS` ⏳ — time to wait to connect a remote host

`TIMEOUTidle = SECONDS` ⏳ — time to keep an idle connection

`TIMEOUTocsp = SECONDS` ⏳ — time to wait to connect an OCSP responder

`transparent = none | source | destination | both` (Unix only) 🫥

enable transparent proxy support on selected platforms. Unix girlies, this one's for you.

Supported values:

`none`

Disable transparent proxy support. This is the default.

`source`

Re-write the address to appear as if a wrapped daemon is connecting from the TLS client machine instead of the machine running stunnel.

This option is currently available in:

Remote mode (connect option) on Linux >=2.6.28

This configuration requires stunnel to be executed as root and without the setuid option.
This configuration requires the following setup for iptables and routing (possibly in /etc/rc.local or equivalent file):

iptables -t mangle -N DIVERT
iptables -t mangle -A PREROUTING -p tcp -m socket -j DIVERT
iptables -t mangle -A DIVERT -j MARK --set-mark 1
iptables -t mangle -A DIVERT -j ACCEPT
ip rule add fwmark 1 lookup 100
ip route add local 0.0.0.0/0 dev lo table 100
echo 0 >/proc/sys/net/ipv4/conf/lo/rp_filter

stunnel must also be executed as root and without the setuid option.

Remote mode (connect option) on Linux 2.2.x

This configuration requires the kernel to be compiled with the transparent proxy option. Connected service must be installed on a separate host. Routing towards the clients has to go through the stunnel box.
stunnel must also be executed as root and without the setuid option.

Remote mode (connect option) on FreeBSD >=8.0

This configuration requires additional firewall and routing setup. stunnel must also be executed as root and without the setuid option.

Local mode (exec option)

This configuration works by pre-loading the libstunnel.so shared library. _RLD_LIST environment variable is used on Tru64, and LD_PRELOAD variable on other platforms.

`destination`

The original destination is used instead of the connect option.

A service section for transparent destination may look like this:

[transparent]
client = yes
accept = <stunnel_port>
transparent = destination

This configuration requires iptables setup to work, possibly in /etc/rc.local or equivalent file.

For a connect target installed on the same host:

/sbin/iptables -t nat -I OUTPUT -p tcp --dport <redirected_port> \
    -m ! --uid-owner <stunnel_user_id> \
    -j DNAT --to-destination <local_ip>:<stunnel_port>

For a connect target installed on a remote host:

/sbin/iptables -I INPUT -i eth0 -p tcp --dport <stunnel_port> -j ACCEPT
/sbin/iptables -t nat -I PREROUTING -p tcp --dport <redirected_port> \
    -i eth0 -j DNAT --to-destination <local_ip>:<stunnel_port>

The transparent destination option is currently only supported on Linux.

`both`

Use both source and destination transparent proxy.

Two legacy options are also supported for backward compatibility:

yes — This option has been renamed to source.
no — This option has been renamed to none.

`verify = LEVEL` 🔎

verify the peer certificate. But bestie, this option is obsolete and should be replaced with the verifyChain and verifyPeer options. It's giving "legacy, but still here" energy.

level 0 — Request and ignore the peer certificate chain.
level 1 — Verify the peer certificate chain if present.
level 2 — Verify the peer certificate chain.
level 3 — Verify the peer certificate chain and the end-entity (leaf) peer certificate against a locally installed certificate.
level 4 — Ignore the peer certificate chain and only verify the end-entity (leaf) peer certificate against a locally installed certificate.
default — No verify.

`verifyChain = yes | no` ⛓️

verify the peer certificate chain starting from the root CA. It's giving "chain of trust" vibes.

For server certificate verification it is essential to also require a specific certificate with checkHost or checkIP. So don't skip that.

The self-signed root CA certificate needs to be stored either in the file specified with CAfile, or in the directory specified with CApath. Pick your path.

default: no

`verifyPeer = yes | no` 👀

verify the end-entity (leaf) peer certificate. The leaf, the final boss of the cert chain.

The end-entity (leaf) peer certificate needs to be stored either in the file specified with CAfile, or in the directory specified with CApath.

default: no

✨ RETURN VALUE ✨

stunnel returns zero on success, non-zero on error. That's it. That's the whole vibe. 💖

✨ SIGNALS ✨

okay bestie, so on Unix you can literally just send stunnel a vibe and it'll do stuff. here's the whole signal menu 💅

SIGHUP — forces a reload of the configuration file. iconic. BUT 🚨 some global options do not get reloaded, no matter how hard you beg:
- chroot
- foreground
- pid
- setgid
- setuid

also, using the setuid option means stunnel can't bind to privileged (<1024) ports while it's reloading the config. so keep that in mind fr.

and when chroot is in play, stunnel goes looking for all its files inside the chroot jail — that's the configuration file, the certificates, the log file, and the pid file. everything. all of it. 🫶

SIGUSR1 — closes and reopens the stunnel log file. this is your log rotation bestie, it's giving "out with the old, in with the new" 🎀
SIGUSR2 — logs the list of active connections. peek at who's connected 👀
SIGTERM, SIGQUIT, SIGINT — shuts stunnel down. bye bye 💀

and if you send literally any other signal? the result is undefined. no cap, don't do it, it's not a vibe check you want to fail.

🌈 EXAMPLES 🌈

giving your local `imapd` service TLS encapsulation 🎀

[imapd]
accept = 993
exec = /usr/sbin/imapd
execArgs = imapd

or, if you're doing remote mode:

[imapd]
accept = 993
connect = 143

letting your local email client talk to a TLS-enabled `imapd` on another server ✨

point the email client at localhost on port 119, and use this:

[imap]
client = yes
accept = 143
connect = servername:993

tunneling to your `pppd` daemon on port 2020 🦋

something like:

[vpn]
accept = 2020
exec = /usr/sbin/pppd
execArgs = pppd local
pty = yes

inetd mode, launching your `imapd` process 👑

use this stunnel.conf. note: there must be no [service_name] section.

exec = /usr/sbin/imapd
execArgs = imapd

setting up a SOCKS VPN — client side 🧦

configure the following client service:

[socks_client]
client = yes
accept = 127.0.0.1:1080
connect = vpn_server:9080
verifyPeer = yes
CAfile = stunnel.pem

and the corresponding config over on the vpn_server host:

[socks_server]
protocol = socks
accept = 9080
cert = stunnel.pem
key = stunnel.key

now test your config on the client machine with:

curl --socks4a localhost http://www.example.com/

an example server mode SNI configuration 💖

[virtual]
; primary service
accept = 443
cert =  default.pem
connect = default.internal.mydomain.com:8080

[sni1]
; secondary service 1
sni = virtual:server1.mydomain.com
cert = server1.pem
connect = server1.internal.mydomain.com:8081

[sni2]
; secondary service 2
sni = virtual:server2.mydomain.com
cert = server2.pem
connect = server2.internal.mydomain.com:8082
verifyPeer = yes
CAfile = server2-allowed-clients.pem

advanced engine config — auth with private keys from the Windows certificate store (Windows only) 🪟

with the CAPI engine you don't have to hand-pick the client key to use. the client key is automatically selected based on the list of CAs trusted by the server. obsessed.

engine = capi

[service]
engineId = capi
client = yes
accept = 127.0.0.1:8080
connect = example.com:8443

advanced engine config — cert + private key from a `pkcs11` engine 🔐

engine = pkcs11
engineCtrl = MODULE_PATH:opensc-pkcs11.so
engineCtrl = PIN:123456

[service]
engineId = pkcs11
client = yes
accept = 127.0.0.1:8080
connect = example.com:843
cert = pkcs11:token=MyToken;object=MyCert
key = pkcs11:token=MyToken;object=MyKey

advanced engine config — cert + private key from a SoftHSM token 🌸

engine = pkcs11
engineCtrl = MODULE_PATH:softhsm2.dll
engineCtrl = PIN:12345

[service]
engineId = pkcs11
client = yes
accept = 127.0.0.1:8080
connect = example.com:843
cert = pkcs11:token=MyToken;object=KeyCert

advanced provider config — cert + private key from a `pkcs11prov` provider ⭐

Note: requires OpenSSL 3.0 or later

setEnv = PKCS11_MODULE_PATH=opensc-pkcs11.dll
setEnv = PKCS11_PIN:123456
provider = pkcs11prov

[service]
client = yes
accept = 127.0.0.1:8080
connect = example.com:843
cert = pkcs11:token=MyToken;object=MyCert
key = pkcs11:token=MyToken;object=MyKey

Note: requires OpenSSL 3.5 or later

provider = pkcs11prov
providerParameter = pkcs11prov:pkcs11_module=opensc-pkcs11.dll
providerParameter = pkcs11prov:pin=123456

[service]
client = yes
accept = 127.0.0.1:8080
connect = example.com:843
cert = pkcs11:token=MyToken;object=MyCert
key = pkcs11:token=MyToken;object=MyKey

On Windows, the PKCS#11 library must live in the ossl-modules directory, or you have to hand over a full absolute path in the PKCS11_MODULE_PATH or pkcs11_module parameter. no shortcuts bestie.

👑 NOTES 👑

RESTRICTIONS

stunnel cannot be used for the FTP daemon, and it's not being dramatic — it's because of the nature of the FTP protocol, which utilizes multiple ports for data transfers. 🙈 there are TLS-enabled versions of FTP and telnet daemons out there though, so go get one of those.

INETD MODE

the most common use of stunnel is to listen on a network port and establish communication with either a new port via the connect option, or a new program via the exec option. but there's a special case where you want some other program to accept incoming connections and launch stunnel — for example with inetd, xinetd, or tcpserver.

say you've got this line in inetd.conf:

imaps stream tcp nowait root /usr/bin/stunnel stunnel /etc/stunnel/imaps.conf

in these cases, the inetd-style program is the one responsible for binding a network socket (imaps above) and handing it over to stunnel the moment a connection comes in. so you do not want stunnel to have any accept option. all the Service Level Options should go in the global options section, and no [service_name] section will be present. check the EXAMPLES section for example configurations 🫶

CERTIFICATES

every TLS-enabled daemon needs to present a valid X.509 certificate to the peer. it also needs a private key to decrypt the incoming data. the easiest way to get a certificate and a key is to generate them with the free OpenSSL package. more info on certificates generation lives on the pages listed below.

the .pem file should contain the unencrypted private key and a signed certificate (not a certificate request). so the file should look like this:

-----BEGIN RSA PRIVATE KEY-----
[encoded key]
-----END RSA PRIVATE KEY-----
-----BEGIN CERTIFICATE-----
[encoded certificate]
-----END CERTIFICATE-----

RANDOMNESS

stunnel needs to seed the PRNG (pseudo-random number generator) so that TLS gets good randomness. these sources are loaded in order until enough random data has been gathered:

the file specified with the RNDfile flag.
the file specified by the RANDFILE environment variable, if set.
the file .rnd in your home directory, if RANDFILE is not set.
the file specified with --with-random at compile time.
the contents of the screen if running on Windows.
the egd socket specified with the EGD flag.
the egd socket specified with --with-egd-sock at compile time.
the /dev/urandom device.

note that on Windows machines without console user interaction (mouse movements, creating windows, etc.) the screen contents are not variable enough to be sufficient, and you should provide a random file for use with the RNDfile flag. 💀

note that the file specified with the RNDfile flag should contain random data — meaning it should contain different information each time stunnel is run. this is handled automatically unless the RNDoverwrite flag is used. if you want to update this file manually, the openssl rand command in recent versions of OpenSSL would be useful. ✨

Important note: if /dev/urandom is available, OpenSSL often seeds the PRNG with it while checking the random state. on systems with /dev/urandom, OpenSSL is likely to use it even though it's listed at the very bottom of the list above. this is the behaviour of OpenSSL and not stunnel — not our fault, not our problem 😭

DH PARAMETERS

stunnel 4.40 and later contains hardcoded 2048-bit DH parameters. starting with stunnel 5.18, these hardcoded DH parameters get replaced every 24 hours with autogenerated temporary DH parameters. DH parameter generation may take several minutes ⏳

alternatively, it's possible to specify static DH parameters in the certificate file, which disables generating temporary DH parameters:

openssl dhparam 2048 >> stunnel.pem

🎀 FILES 🎀

@sysconfdir@/stunnel/stunnel.conf — the stunnel configuration file. that's the one, that's the moment 💅

💀 BUGS 💀

the execArgs option and the Win32 command line do not support quoting. yes, really. it's giving chaos.

💜 SEE ALSO 💜

tcpd(8) — access control facility for internet services
inetd(8) — internet 'super-server'
http://www.stunnel.org/ — stunnel homepage
http://www.openssl.org/ — OpenSSL project website

🌟 AUTHOR 🌟

Michał Trojnara — <Michal.Trojnara@stunnel.org> 💖

and that's a wrap on the whole page bestie!! this is stunnel version 5.77, dated 2026.02.18, and it's the stunnel(8) manual page — go forth and tunnel, you absolute icon 👑✨💅

📦 where this page comes from

ubuntu resolute: stunnel4 3:5.77-1 · GPL-2+-openssl
💖 girlified by deepseek-ai/DeepSeek-V4.1-Flash on 2026-10-18: a language model's rewrite of the original, under its terms

stunnel(8)

🦋 stunnel(8) — TLS offloading and load-balancing proxy 🦋

✨ NAME ✨

🌸 SYNOPSIS 🌸

💖 DESCRIPTION 💖

👑 OPTIONS 👑

🌈 CONFIGURATION FILE 🌈

💅 GLOBAL OPTIONS 💅

🎀 SERVICE-LEVEL OPTIONS 🎀

protocol = PROTO

protocolAuthentication = AUTHENTICATION

protocolDomain = DOMAIN

protocolHeader = HEADER

protocolHost = ADDRESS

protocolPassword = PASSWORD

protocolUsername = USERNAME

PSKidentity = IDENTITY

PSKsecrets = FILE

pty = yes | no (Unix only)

redirect = [HOST:]PORT

renegotiation = yes | no

reset = yes | no

retry = yes | no | DELAY

securityLevel = LEVEL

requireCert = yes | no

setgid = GROUP (Unix only)

setuid = USER (Unix only)

sessionCacheSize = NUM_ENTRIES

sessionCacheTimeout = TIMEOUT

sessionResume = yes | no

sessiond = HOST:PORT

sni = SERVICE_NAME:SERVER_NAME_PATTERN (server mode)

sni = SERVER_NAME (client mode) 🎀

socket = a|l|r:OPTION=VALUE[:VALUE] 🧦

sslVersion = SSL_VERSION 🌈

sslVersionMax = SSL_VERSION 🔝

sslVersionMin = SSL_VERSION 🔻

stack = BYTES (except for FORK model) 🥞

ticketKeySecret = SECRET 🎟️

ticketMacSecret = SECRET 🔐

TIMEOUTbusy = SECONDS ⏳ — time to wait for expected data

TIMEOUTclose = SECONDS ⏳ — time to wait for close_notify (set to 0 for buggy MSIE)

TIMEOUTconnect = SECONDS ⏳ — time to wait to connect a remote host

TIMEOUTidle = SECONDS ⏳ — time to keep an idle connection

TIMEOUTocsp = SECONDS ⏳ — time to wait to connect an OCSP responder

transparent = none | source | destination | both (Unix only) 🫥

none

source

destination

both

verify = LEVEL 🔎

verifyChain = yes | no ⛓️

verifyPeer = yes | no 👀

✨ RETURN VALUE ✨

✨ SIGNALS ✨

🌈 EXAMPLES 🌈

giving your local imapd service TLS encapsulation 🎀

letting your local email client talk to a TLS-enabled imapd on another server ✨

tunneling to your pppd daemon on port 2020 🦋

inetd mode, launching your imapd process 👑

setting up a SOCKS VPN — client side 🧦

an example server mode SNI configuration 💖

advanced engine config — auth with private keys from the Windows certificate store (Windows only) 🪟

advanced engine config — cert + private key from a pkcs11 engine 🔐

advanced engine config — cert + private key from a SoftHSM token 🌸

advanced provider config — cert + private key from a pkcs11prov provider ⭐

👑 NOTES 👑

RESTRICTIONS

INETD MODE

CERTIFICATES

RANDOMNESS

DH PARAMETERS

🎀 FILES 🎀

💀 BUGS 💀

💜 SEE ALSO 💜

🌟 AUTHOR 🌟

`protocol = PROTO`

`protocolAuthentication = AUTHENTICATION`

`protocolDomain = DOMAIN`

`protocolHeader = HEADER`

`protocolHost = ADDRESS`

`protocolPassword = PASSWORD`

`protocolUsername = USERNAME`

`PSKidentity = IDENTITY`

`PSKsecrets = FILE`

`pty = yes | no (Unix only)`

`redirect = [HOST:]PORT`

`renegotiation = yes | no`

`reset = yes | no`

`retry = yes | no | DELAY`

`securityLevel = LEVEL`

`requireCert = yes | no`

`setgid = GROUP (Unix only)`

`setuid = USER (Unix only)`

`sessionCacheSize = NUM_ENTRIES`

`sessionCacheTimeout = TIMEOUT`

`sessionResume = yes | no`

`sessiond = HOST:PORT`

`sni = SERVICE_NAME:SERVER_NAME_PATTERN (server mode)`

`sni = SERVER_NAME` (client mode) 🎀

`socket = a|l|r:OPTION=VALUE[:VALUE]` 🧦

`sslVersion = SSL_VERSION` 🌈

`sslVersionMax = SSL_VERSION` 🔝

`sslVersionMin = SSL_VERSION` 🔻

`stack = BYTES` (except for FORK model) 🥞

`ticketKeySecret = SECRET` 🎟️

`ticketMacSecret = SECRET` 🔐

`TIMEOUTbusy = SECONDS` ⏳ — time to wait for expected data

`TIMEOUTclose = SECONDS` ⏳ — time to wait for `close_notify` (set to `0` for buggy MSIE)

`TIMEOUTconnect = SECONDS` ⏳ — time to wait to connect a remote host

`TIMEOUTidle = SECONDS` ⏳ — time to keep an idle connection

`TIMEOUTocsp = SECONDS` ⏳ — time to wait to connect an OCSP responder

`transparent = none | source | destination | both` (Unix only) 🫥

`none`

`source`

`destination`

`both`

`verify = LEVEL` 🔎

`verifyChain = yes | no` ⛓️

`verifyPeer = yes | no` 👀

giving your local `imapd` service TLS encapsulation 🎀

letting your local email client talk to a TLS-enabled `imapd` on another server ✨

tunneling to your `pppd` daemon on port 2020 🦋

inetd mode, launching your `imapd` process 👑

advanced engine config — cert + private key from a `pkcs11` engine 🔐

advanced provider config — cert + private key from a `pkcs11prov` provider ⭐