This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages)
|
Stunnel is an open-source multi-platform application used to provide a universal TLS/SSL tunneling service.
 | |
| Developer(s) | Michał Trojnara |
|---|---|
| Initial release | 11 February 1998[1] |
| Stable release | 5.72[2] 
/ 4 February 2024 |
| Repository | www |
| Written in | C[3] |
| Operating system | Multi-platform |
| Type | Proxy, Encryption |
| License | GNU General Public License |
| Website | www |
Stunnel is used to provide secure encrypted connections for clients or servers that do not speak TLS or SSL natively.[4] It runs on a variety of operating systems,[5] 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.[6]
If linked against libwrap, it can be configured to act as a proxy–firewall service as well.[citation needed]
Stunnel is maintained by Polish programmer Michał Trojnara and released under the terms of the GNU General Public License (GPL) with OpenSSL exception.[7]
Example
editA stunnel can be used 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, the stunnel would be configured 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 and 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).[citation needed]
See also
editReferences
edit- ^ "stunnel change log". stunnel.org. Retrieved 2 March 2024.
- ^ "stunnel change log". Retrieved 2 March 2024.
- ^ Trojnara, Michał. "stunnel sources". GitHub. Retrieved 12 May 2020.
- ^ O'Donovan, Barry (October 2004). "Secure Communication with Stunnel". Linux Gazette, Issue 107.
- ^ ""stunnel: Ports"". Archived from the original on 1 April 2019. Retrieved 24 August 2020.
- ^ "stunnel(8) manual"
- ^ "stunnel license (see COPYRIGHT.md for detailed GPL conditions)". stunnel.org. Retrieved 2 March 2024.
