31. October 2001: Workarounds for Windows 98, ME and 2000 have been found by Jum Dunphy.
26. December 2000: Upgraded my patched version and windows binaries to version 3.11
06. September 2000: Stunnel now supports SAMBA over SSL, as SSLProxy did before, using the new "-n smb" option.

Hints on using stunnel with a Windows (TM) operating system

As far as I know, stunnel works only with one version of Windows: Windows NT 4. I heard that it doesn't run on Windows 95, 98, 2000. The reason for this is: Windows 95/98 can't map a share from an IP-address (and you would need to use \\\share) (Update: Jim Dunphy reports, Windows 98 & ME work, if you use \\localhost\share instead of the ip address), and in Windows 2000 it seems, the operating system itself is catching the port 139, and stunnel does not receive the connection. (Another update from Jim: "The trick with 2000 is to place stunnel on or disable the 'server' service and it will work on")

If you need to create a network connection from your Windows 95/98/2000 computer to another computer at a remote location using Samba over SSL, I recommend to use a second computer in your office running Linux or any other "real" operating system.

You can use another computer that is in your location as the tunnel gateway computer. Run the stunnel program on the gateway computer. Usually port 139 is free on a Linux computer - if not, add another ip address to the Linux computer and bind stunnel to that address. Store a mapping from a name to the stunnel ip address in your WINS server (if required) to allow for entering something like \\name\share on your Windows box. Your Windows box will then connect to your local Linux computer unencrypted, the stunnel running there will encrypt and communicate with the remote site. Multiple users in your office can share this stunnel process. For each remote destination site you need a separately running stunnel process, all of them may run on the same computer, but for each your local gateway computer needs a seperate IP adress. Well, I have not tried, but it might work to use a Windows NT 4 computer as your local stunnel gateway computer.

What I provide

I'm providing a precompiled Windows version of Stunnel. This is for your convenience - you don't need to compile it yourself. This program is based on stunnel-3.11 as avaiable on or, linked with OpenSSL version 0.9.6.

I created a version stunnel-3.11kai, which includes smb negotiation and some windows GUI code, which was created using a patch initially contributed by Robert Spier. You can download my patched source version here: stunnel-3.11-kai-gui.tar.gz (right click, save as...). Windows users might prefer the archive in zip format. I added MSVC Makefiles (stunnel.dsp / stunnelw.dsp) that create a console / GUI executable.

You can download a precompiled Windows binary version from here: and a detached pgp signature here. My public PGP key is here.

Inside the archive you will find the OpenSSL 0.9.6 DLLs and two executables: stunnel.exe (console version) and stunnelw.exe (GUI version that integrates into the system tray).

Please go to or to get further documentation / information about the Stunnel software.

Best regards
Kai Engert,

SSL Proxy

Historical message: Thanks for your interest in SSLProxy, but I decided to stop my work on SSLProxy.
That should not be a problem for you, because you can use Stunnel instead.
Stunnel is very similar to SSLProxy, but I think it's much better, and most importantly it's more actively maintained than SSLProxy was in the past.

If you still are interested in the (obsolete) SSLProxy, you can find the old SSLProxy page here.


Besides from the existing projects OpenSSL and OpenSSH, I heard about a project implementing SSH and SCP for Windows systems. I have not tried the tools available there, but you might be interested in:
Disclaimer: Linux is a registered trademark of Linus Torvalds. Windows is a registered trademark of Microsoft.
Stunnel is free software and provided AS IS, WITHOUT ANY GUARANTEES.