Stunnel: Difference between revisions
m Dating maintenance tags: {{Cn}} |
Removed unsourced promotion of different software. |
||
Line 22: | Line 22: | ||
If [[Linker (computing)|linked]] against [[TCP Wrapper|libwrap]], it can be configured to act as a [[proxy server|proxy]]–[[firewall (networking)|firewall]] service as well. |
If [[Linker (computing)|linked]] against [[TCP Wrapper|libwrap]], it can be configured to act as a [[proxy server|proxy]]–[[firewall (networking)|firewall]] service as well. |
||
Stunnel is maintained by Michał Trojnara and released under the terms of the [[GNU General Public License]] (GPL) with [[OpenSSL]] exception. |
Stunnel is maintained by Michał Trojnara and released under the terms of the [[GNU General Public License]] (GPL) with [[OpenSSL]] exception. |
||
==Example scenario== |
==Example scenario== |
Revision as of 14:38, 27 February 2020
Developer(s) | Michał Trojnara |
---|---|
Initial release | 10 December 1998citation needed] | [
Stable release | 5.55
/ 10 June 2019[1] |
Repository | www |
Written in | C++[citation needed] |
Operating system | Multi-platform |
Type | Proxy, Encryption |
License | GNU General Public License |
Website | www |
Stunnel is an open-source multi-platform application used to provide a universal TLS/SSL tunneling service.
Stunnel can be used to provide secure encrypted connections for clients or servers that do not speak TLS or SSL natively.[2] It runs on a variety of operating systems,[3] including most Unix-like operating systems and Windows. Stunnel relies on the OpenSSL library to implement the underlying TLS or SSL protocol.
Stunnel uses public-key cryptography with X.509 digital certificates to secure the SSL connection, and clients can optionally be authenticated via a certificate.[4]
If linked against libwrap, it can be configured to act as a proxy–firewall service as well.
Stunnel is maintained by Michał Trojnara and released under the terms of the GNU General Public License (GPL) with OpenSSL exception.
Example scenario
For example, one could use stunnel to provide a secure SSL connection to an existing non-SSL-aware SMTP mail server. Assuming the SMTP server expects TCP connections on port 25, one would configure stunnel to map the SSL port 465 to non-SSL port 25. A mail client connects via SSL to port 465. Network traffic from the client initially passes over SSL to the stunnel application, which transparently encrypts/decrypts traffic and forwards unsecured traffic to port 25 locally. The mail server sees a non-SSL mail client.[citation needed]
The stunnel process could be running on the same or a different server from the unsecured mail application; however, both machines would typically be behind a firewall on a secure internal network (so that an intruder could not make its own unsecured connection directly to port 25).
References
- ^ Trojnara, Michał. "Downloads". Stunnel. Retrieved 6 July 2019.
- ^ O'Donovan, Barry (October 2004). "Secure Communication with Stunnel". Linux Gazette, Issue 107.
- ^ "stunnel: Ports"
- ^ "stunnel(8) manual"