Am in the midst of building stunnel docker container.
Eventually this will be summarized on Stunnel/Docker
But until then the notes are taking shape at Docker/Pods/Wifi
Running stunnel as a server: Stunnel/Server
Running stunnel as a client: Stunnel/Client
Troubleshooting Stunnel: Stunnel/Troubleshooting
For more information about certificates in stunnel, see Stunnel/Certificates
You have two options for getting a certificate to run an stunnel server.
Option 1 is to use Let's Encrypt to get a signed SSL certificate (recommended): LetsEncrypt
Option 2 is to go the self-signed certificate route: RaspberryPi/SSH Stunnel
Running Services Over Stunnel
Running SSH over Stunnel: RaspberryPi/SSH Stunnel
Running HTTP over Stunnel: Stunnel/HTTP
Running Rsync over Stunnel: Stunnel/Rsync
Running SCP (secure copy) over Stunnel: Stunnel/Scp
2016-2017 UGR wifi project made use of Stunnel to bypass a network firewall that restricted traffic to ports 80 and 443 only and allow Raspberry Pi computers to communicate with a central command-and-control server.
Building an Stunnel to carry SSH traffic: RaspberryPi/SSH Stunnel
Building an Stunnel to carry a reverse SSH connection: RaspberryPi/Reverse SSH Stunnel
Running OpenVPN through Stunnel: OpenVPN/Stunnel
Stunnel alternatives: Stunnel_Alternatives
stunnelsecure tunnel - create secure encrypted connections on any port to wrap any protocol
Stunnel Over Docker: Stunnel/Docker
Flags · Template:StunnelFlag · e