Added "direct" protocol. It's very similar to socks5, but doesn't have excess socks5's handshakes, which increase latency in a case of "socks" protocol in stunnel.conf file. "direct" protocol doesn't use "auth" handshake and sends data directly with TLS tunnel. In my case, I was able to reduce latency from 450 ms to 250 ms. This is noticeable when you use stunnel as a "VPN" with REDIRECT or as a socks5 client to serf internet. However, if you still need socks5 client on stunnel client's side, you can use "direct:socks5" protocol together with "direct" protocol on a server's side. You can check all the changes in the following commit: https://github.com/stavultras/stunnel/commit/f21f49c25ddcbfd1c07ec3674ea8ab6cfb0f99d6
The stunnel program is designed to work as an SSL encryption wrapper between remote client and local (inetd-startable) or remote servers. The goal is to facilitate SSL encryption and authentication for non-SSL-aware programs.
stunnel can be used to add SSL functionality to commonly used inetd daemons like POP-2, POP-3 and IMAP servers without any changes in the programs' code.
- COPYING A short license overview
- COPYRIGHT The complete terms and conditions
- CREDITS A list of major contributions
- NEWS What I did
- TODO What I'm going to do
- BUGS Known bugs
- INSTALL.FIPS, INSTALL.W32 and INSTALL.WCE Additional installation notes
- PORTS Known ports