Stunnel - Revision history

Admin: /* Case Studies */

2017-04-30T08:33:45Z

Case Studies

← Older revision		Revision as of 08:33, 30 April 2017
Line 41:		Line 41:
	==Case Studies==		==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.		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]]		See [[Docker/Pods/Wifi]]

2017-04-30T08:33:38Z

Case Studies

← Older revision		Revision as of 08:33, 30 April 2017
Line 43:		Line 43:
	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.		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/~~Boats~~/Wifi]]		See [[Docker/Pods/Wifi]]

	=Older=		=Older=

2017-04-30T08:33:26Z

Certificates

← Older revision		Revision as of 08:33, 30 April 2017
Line 20:		Line 20:

	==Certificates==		==Certificates==

			For more information about certificates in stunnel, see [[Stunnel/Certificates]]

	You have two options for getting a certificate to run an stunnel server.		You have two options for getting a certificate to run an stunnel server.

2017-04-29T22:35:40Z

Running Services Over Stunnel

← Older revision		Revision as of 22:35, 29 April 2017
Line 35:		Line 35:
	Running Rsync over Stunnel: [[Stunnel/Rsync]]		Running Rsync over Stunnel: [[Stunnel/Rsync]]

	Running SCP (secure copy) over Stunnel: [[Stunnel/~~SCP~~]]		Running SCP (secure copy) over Stunnel: [[Stunnel/Scp]]

	==Case Studies==		==Case Studies==

2017-04-29T22:29:47Z

Running Services Over Stunnel

← Older revision		Revision as of 22:29, 29 April 2017
Line 32:		Line 32:

	Running HTTP over Stunnel: [[Stunnel/HTTP]]		Running HTTP over Stunnel: [[Stunnel/HTTP]]

			Running Rsync over Stunnel: [[Stunnel/Rsync]]

			Running SCP (secure copy) over Stunnel: [[Stunnel/SCP]]

	==Case Studies==		==Case Studies==

2017-04-29T22:29:02Z

Newer (2017)

← Older revision		Revision as of 22:29, 29 April 2017
Line 5:		Line 5:
	Eventually this will be summarized on [[Stunnel/Docker]]		Eventually this will be summarized on [[Stunnel/Docker]]

	But until then the notes are taking shape at [[Docker/~~Boats~~/Wifi]]		But until then the notes are taking shape at [[Docker/Pods/Wifi]]

	==Installing==		==Installing==

2017-03-30T21:08:32Z

Running Client/Server

← Older revision		Revision as of 21:08, 30 March 2017
Line 18:		Line 18:

	Troubleshooting Stunnel: [[Stunnel/Troubleshooting]]		Troubleshooting Stunnel: [[Stunnel/Troubleshooting]]

			==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 Services Over Stunnel==

2017-03-29T23:27:42Z

Case Studies

← Older revision		Revision as of 23:27, 29 March 2017
Line 28:		Line 28:

	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.		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/Boats/Wifi]]

	=Older=		=Older=

2017-03-29T23:26:55Z

Running Services Over Stunnel

← Older revision		Revision as of 23:26, 29 March 2017
Line 25:		Line 25:
	Running HTTP over Stunnel: [[Stunnel/HTTP]]		Running HTTP over Stunnel: [[Stunnel/HTTP]]

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

	=Older=		=Older=

2017-03-29T23:25:50Z

← Older revision		Revision as of 23:25, 29 March 2017
Line 1:		Line 1:
	==Newer (2017)==		=Newer (2017)=

	Am in the midst of building stunnel docker container.		Am in the midst of building stunnel docker container.
Line 6:		Line 6:

	But until then the notes are taking shape at [[Docker/Boats/Wifi]]		But until then the notes are taking shape at [[Docker/Boats/Wifi]]

			==Installing==

	Installing: [[Stunnel/Installing]]		Installing: [[Stunnel/Installing]]

			==Running Client/Server==

	Running stunnel as a server: [[Stunnel/Server]]		Running stunnel as a server: [[Stunnel/Server]]
Line 14:		Line 18:

	Troubleshooting Stunnel: [[Stunnel/Troubleshooting]]		Troubleshooting Stunnel: [[Stunnel/Troubleshooting]]

			==Running Services Over Stunnel==

			Running SSH over Stunnel: [[RaspberryPi/SSH Stunnel]]

			Running HTTP over Stunnel: [[Stunnel/HTTP]]



	==Older==		=Older=

	Building an Stunnel to carry SSH traffic: [[RaspberryPi/SSH Stunnel]]		Building an Stunnel to carry SSH traffic: [[RaspberryPi/SSH Stunnel]]