![]() On the client side, you setup any authentication/encryption method set on the server, and simply forward a local port to the stunnel SOCKS port on the server. You can use either PKI systems (with CA, client/server certs, CRL, OSCP, etc), or just a simple PSKsecrets file. This ensures that the underlying SOCKS traffic is fully authenticated and encrypted. This is your typical SOCKS4a/5 protocol, supporting basic features like name resolution and TCP/IP stream connection.Īccessing to that SOCKS port on the server, is guarded by the stunnel authentication layer. On the server side, stunnel exposes a SOCKS port. The setup is easy and straight forward and what is happening under the hood, is rather interesting: Server side How to install and configure stunnel on Ubuntu Process overview To see how to properly install and setup stunnel on Ubuntu (and possibly other distros), refer to my other article on the topic:
0 Comments
Leave a Reply. |