From charlesreid1

(Created page with "==Stunnel Client== Running an stunnel client requires installing stunnel and setting up a configuration file just like if you were setting up an Stunnel/Server. If we w...")
 
Line 1: Line 1:
==Stunnel Client==
==Stunnel Client==


Running an stunnel client requires installing stunnel and setting up a configuration file just like if you were setting up an [[Stunnel/Server]].  
Running an stunnel client requires installing stunnel and setting up a configuration file just like if you were setting up an [[Stunnel/Server]], except swapping the accept and connect ports, since we want the client to accept local traffic (on port 8443) and send it on to the server that it connects to with SSL (on port 443).


If we want to establish a connection on port 443 (externally) to forward on to port 8443 (locally), we can use the following config file:
If we want to establish a connection on port 443 (externally) to forward on to port 8443 (locally), we can use the following config file:
Line 15: Line 15:
connect = 10.11.12.13:443
connect = 10.11.12.13:443
</pre>
</pre>


==Flags==
==Flags==

Revision as of 03:00, 28 March 2017

Stunnel Client

Running an stunnel client requires installing stunnel and setting up a configuration file just like if you were setting up an Stunnel/Server, except swapping the accept and connect ports, since we want the client to accept local traffic (on port 8443) and send it on to the server that it connects to with SSL (on port 443).

If we want to establish a connection on port 443 (externally) to forward on to port 8443 (locally), we can use the following config file:

output  = /var/log/stunnel4/stunnel.log
cert    = /usr/local/etc/stunnel/stunnel.pem
key     = /usr/local/etc/stunnel/stunnel.pem
pid     = /var/run/stunnel4/stunnel.pid
client  = yes
[https]
accept  = 127.0.0.1:8443
connect = 10.11.12.13:443

Flags