Patch info for wingui_rspier

Author Comments

Please find attached an alpha release patch to the current version of
stunnel to provide a Win32 UI for it.

The idea, was that people who refused to switch to a SSL supporting
MUA, could use this.

It still requires command line arguments, but log output now goes into
a window, and the program lives in the Tray.  To configure multiple
tunnels, create a Shortcut (.lnk file).

This code is not well tested - I created it for a specific need I had
- and it seems to work for that.  If it eats your hard drive or burns
your house down, it is not my fault.  Use at your own risk.

It makes no changes to how stunnel "the guts" works itself, only minor
modifications to how logs are ouput.

Please send feedback/buglets to the list.

(Note: the build process has changed slightly.  This creates a
stunnelw.exe binary.  When you do a plain 'make' it will explain things.
You _must_ do a make clean between building stunnel.exe and
stunnelw.exe.  mingw is required, because their resource compiler
is hardcoded into the makefile)

-R


There is a binary at http://www.pobox.com/~rspier/tmp/stunnelw.exe
(location is _NOT_ permanant.)

You will need to acquire the libssl32.dll and libeay32.dll yourself.
There are binaries on the stunnel website, but I've had trouble
getting them to work with Win98.

Compiling stunnel is trivial.  The tools are free.  It just takes a
while to compile the dll's.  I reccomend you try it yourself.

-R

This website makes patches available for use by the Internet community. However it does not endorse any of the patches contained herein. They could be work perfectly, or totally foul up everything. We don't know. Contact the authors if you have any questions. Use at your own risk.

The Stunnel software package does not contain any cryptography itself, however please remember that import and/or export of cryptographic software, code providing hooks to cryptographic algorithms, and discussion about cryptography is illegal in some countries. It is imperative for you to know your local laws governing cryptography. We're not liable for anything you do that violates your local laws.