stunnel: Authentication

Either the TLS client, the TLS server, or both need to be authenticated:

  • Server authentication prevents Man-In-The-Middle (MITM) attacks on the encryption protocol.
  • Client authentication allows for restricting access for individual clients (access control).


The easiest way to configure authentication is with PSK (Pre-Shared Key). It provides both client and server authentication. PSK is also the fastest TLS authentication.


PSK authentication requires stunnel version 5.09 or higher.

Server Configuration

A trivial configuration example:

[PSK server]
accept = <server_port>
connect = <dst_port>
ciphers = PSK
PSKsecrets = psk.txt

The psk.txt file contains one line for each client:


Client Configuration

A trivial configuration example:

[PSK client 1]
client = yes
accept =<src_port>
connect = <server_host>:<server_port>
PSKsecrets = psk1.txt

The psk1.txt file only needs a single line:


Each client needs a separate secret. Otherwise, all the clients sharing the same key will have to be reconfigured if the key is compromised.


For simplicity, this tutorial only covers server authentication. The advantage of this configuration is that it does not require individual secrets for each of the clients.

Server Configuration

Unless PSK authentication is configured, each stunnel server needs a certificate with the corresponding private key. The Windows installer of stunnel automatically builds a certificate. On Unix platforms, a certificate can be built with "make cert". A certificate can also be purchased from one of the available commercial certificate authorities.

A trivial configuration example:

[certificate-based server]
accept = <server_port>
connect = <dst_port>
cert = cert.pem
key = key.pem

The "key" option may be omitted if cert.pem also contains the private key.

Client Configuration

stunnel can use an existing PKI (Public Key Infrastructure). The following configuration requires stunnel 5.15 or later:

[PKI client]
client = yes
accept =<src_port>
connect = <server_host>:<server_port>
verifyChain = yes
CAfile = ca-certs.pem
checkHost = <server_host>

The ca-certs.pem file contains the certificates of trusted certificate authorities.

Alternatively, a technique known as certificate pinning can be used. The following configuration requires stunnel version 4.46 or higher:

[pinning client]
client = yes
accept =<src_port>
connect = <server_host>:<server_port>
verifyPeer = yes
CAfile = peer-certificate.pem

The peer-certificate.pem file needs to contain the server certificate.

0 (0)
Article Rating (No Votes)
Rate this article
There are no attachments for this article.
There are no comments for this article. Be the first to post a comment.
Full Name
Email Address
Security Code Security Code
Related Articles RSS Feed
Viewed 6403 times since Sat, Jun 2, 2018
RHEL: Services basic management - chkconfig
Viewed 3668 times since Sat, Jun 2, 2018
Linux: how to monitor the nofile limit
Viewed 7950 times since Wed, Jul 25, 2018
How To Create a Linux Swap File
Viewed 1274 times since Fri, Jun 8, 2018
Prosty skaner portów TCP w bash
Viewed 1659 times since Thu, May 24, 2018
RHCS6: Mirror/unmirror a GFS2 volume
Viewed 3866 times since Sun, Jun 3, 2018
Inxi – A Powerful Feature-Rich Commandline System Information Tool for Linux
Viewed 17653 times since Sat, Jun 2, 2018
Enabling or disabling a repository using Red Hat Subscription Management
Viewed 2037 times since Mon, Oct 29, 2018
Using stunnel and TinyProxy to obfuscate HTTP traffic
Viewed 3024 times since Fri, Sep 28, 2018
chrt command: Set / Manipulate Real Time Attributes of a Linux Process
Viewed 9316 times since Mon, Feb 17, 2020