Stunnel: Difference between revisions
From charlesreid1
No edit summary |
|||
| (18 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
=Newer (2017)= | |||
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]] | |||
==Installing== | |||
Installing: [[Stunnel/Installing]] | |||
==Running Client/Server== | |||
Running stunnel as a server: [[Stunnel/Server]] | |||
Running stunnel as a client: [[Stunnel/Client]] | |||
Troubleshooting Stunnel: [[Stunnel/Troubleshooting]] | |||
==Certificates== | |||
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]] | |||
==Case Studies== | |||
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. | |||
See [[Docker/Pods/Wifi]] | |||
=Older= | |||
Building an Stunnel to carry SSH traffic: [[RaspberryPi/SSH Stunnel]] | Building an Stunnel to carry SSH traffic: [[RaspberryPi/SSH Stunnel]] | ||
| Line 6: | Line 54: | ||
Stunnel alternatives: [[Stunnel_Alternatives]] | Stunnel alternatives: [[Stunnel_Alternatives]] | ||
=Flags= | =Flags= | ||
{{ | {{StunnelFlag}} | ||
Latest revision as of 08:33, 30 April 2017
Newer (2017)
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
Installing
Installing: Stunnel/Installing
Running Client/Server
Running stunnel as a server: Stunnel/Server
Running stunnel as a client: Stunnel/Client
Troubleshooting Stunnel: Stunnel/Troubleshooting
Certificates
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
Case Studies
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.
See Docker/Pods/Wifi
Older
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
Flags
 |
stunnel secure tunnel - create secure encrypted connections on any port to wrap any protocol
Using: Client: Stunnel/Client Server: Stunnel/Server Stunnel Over Docker: Stunnel/Docker Certificates: Stunnel/Certificates
Protocols: Stunnel/Rsync · Stunnel/SSH · Stunnel/Scp · Stunnel/HTTP · Stunnel/OpenVPN
Other Links: RaspberryPi/Headless · RaspberryPi/Reverse SSH Category:Stunnel · Category:SSH · Category:Networking
|