RaspberryPi/SSH Stunnel - Revision history

Admin: /* Generate Private Keys/Certificates for SSL */

2017-04-30T09:07:57Z

Generate Private Keys/Certificates for SSL

← Older revision		Revision as of 09:07, 30 April 2017
Line 23:		Line 23:
	</pre>		</pre>

	==Generate Private Keys/Certificates for SSL==		==Generate Private Keys and Certificates for SSL==

	Now you need to generate private keys, so that stunnel has private keys to use when encrypting using SSL.		Now you need to generate private keys, so that stunnel has private keys to use when encrypting using SSL.

2016-02-02T06:22:14Z

2016-02-02T05:30:28Z

Edit Configuration

2016-01-17T17:40:41Z

Reverse SSH Stunnel

← Older revision		Revision as of 17:40, 17 January 2016
Line 292:		Line 292:
	=Reverse SSH Stunnel=		=Reverse SSH Stunnel=

	See the [[RaspberryPi/Reverse SSH Stunnel]] article ~~for how to set up stunnel to work with a reverse SSH connection~~.		This is just part 1 of the trick. Being able to automatically open an SSH tunnel over an arbitrary port is critical to bypassing a firewall, but right now the trick isn't particularly useful, since we aren't usually sitting in front of our Raspberry Pi - we are usually sitting in front of our command-and-control server.

			Part 2 of this trick will show you how to set up a reverse SSH connection, so that when the Pi connects to the command-and-control server, it sets up a tunnel that reverse connections can then use. See the [[RaspberryPi/Reverse SSH Stunnel]] article.

2015-09-25T03:50:33Z

2015-08-04T21:20:55Z

← Older revision		Revision as of 21:20, 4 August 2015
Line 293:		Line 293:

	See the [[RaspberryPi/Reverse SSH Stunnel]] article for how to set up stunnel to work with a reverse SSH connection.		See the [[RaspberryPi/Reverse SSH Stunnel]] article for how to set up stunnel to work with a reverse SSH connection.




			[[Category:Kali]]
			[[Category:Raspberry Pi]]
			[[Category:Networking]]
			[[Category:SSH]]

2015-08-04T21:20:27Z

← Older revision		Revision as of 21:20, 4 August 2015
Line 287:		Line 287:

	That SSH traffic is routed to port 443, where stunnel is listening. Stunnel wraps the SSH traffic going through port 443 in an SSL layer, than sends that SSL traffic out and over port 443 to our remote command and control server. The remote command and control server, which also has stunnel running, listens on port 443, and when it finds traffic, decrypts it and reroutes it to local host port 22, where it looks like regular SSH traffic.		That SSH traffic is routed to port 443, where stunnel is listening. Stunnel wraps the SSH traffic going through port 443 in an SSL layer, than sends that SSL traffic out and over port 443 to our remote command and control server. The remote command and control server, which also has stunnel running, listens on port 443, and when it finds traffic, decrypts it and reroutes it to local host port 22, where it looks like regular SSH traffic.



			=Reverse SSH Stunnel=

			See the [[RaspberryPi/Reverse SSH Stunnel]] article for how to set up stunnel to work with a reverse SSH connection.

2015-08-04T21:09:45Z

Edit Configuration

← Older revision		Revision as of 21:09, 4 August 2015
Line 96:		Line 96:
	<pre>		<pre>
	output = /var/log/stunnel4/stunnel.log		output = /var/log/stunnel4/stunnel.log
	cert=/etc/~~ssl~~/stunnel.pem		cert=/etc/stunnel/stunnel.pem
	key=/etc/~~ssl~~/stunnel.pem		key=/etc/stunnel/stunnel.pem
	pid=/var/run/stunnel4/stunnel.pid		pid=/var/run/stunnel4/stunnel.pid
	client=yes		client=yes

2015-08-04T21:08:19Z

Edit Configuration

← Older revision		Revision as of 21:08, 4 August 2015
Line 98:		Line 98:
	cert=/etc/ssl/stunnel.pem		cert=/etc/ssl/stunnel.pem
	key=/etc/ssl/stunnel.pem		key=/etc/ssl/stunnel.pem
	pid=/var/run/stunnel.pid		pid=/var/run/stunnel4/stunnel.pid
	client=yes		client=yes
	[ssh]		[ssh]

2015-08-04T21:07:31Z

Open Your Firewall to SSL

← Older revision		Revision as of 21:07, 4 August 2015
Line 249:		Line 249:

	iptables -A INPUT -p tcp --dport 443 -j ACCEPT		iptables -A INPUT -p tcp --dport 443 -j ACCEPT
			</pre>

			==Restart stunnel==

			<pre>
			$ /etc/init.d/stunnel4 restart
	</pre>		</pre>