I installed the official stunnel 4.33 binary on Windows XP/32.
And, when I execute "stunnel -version", a popup window appears with the following message:
--------------------------- stunnel 4.33 on Win32 (not configured) --------------------------- Stunnel server is down due to an error. You need to exit and correct the problem. Click OK to see the error log window. --------------------------- OK ---------------------------
Shouldn't that just work? What may be the cause for the problem?
Indeed, I didn't configure stunnel yet. But I also realized that when I change something - for example the log level - in "stunnel.conf", then this is ignored by "stunnel -version".
After clicking "OK" to close the popup message, I get some more info, though meaningless to me:
stunnel 4.33 on x86-pc-mingw32-gnu with OpenSSL 1.0.0 29 Mar 2010 Threading:WIN32 SSL:ENGINE Sockets:SELECT,IPv6
Global options debug = notice RNDbytes = 64 RNDoverwrite = yes service = stunnel taskbar = yes
Service-level options cert = stunnel.pem ciphers = ALL:!aNULL:!eNULL:!SSLv2 session = 300 seconds stack = 65536 bytes sslVersion = SSLv3 for client, all for server TIMEOUTbusy = 300 seconds TIMEOUTclose = 60 seconds TIMEOUTconnect = 10 seconds TIMEOUTidle = 43200 seconds verify = none
Server is down
On Fri, 2010-08-27 08:36:52 +0000, Felix E. Klee wrote:
I installed the official stunnel 4.33 binary on Windows XP/32.
And, when I execute "stunnel -version", a popup window appears with the following message:
stunnel 4.33 on Win32 (not configured)
Felix,
"not configured" is a fixed text. I suppose it wants to say the Makefile et al. weren't created by the ./configure script (in contrast to e.g. stunnel on POSIX operating systems).
Stunnel server is down due to an error. You need to exit and correct the problem. Click OK to see the error log window.
OK
Shouldn't that just work? What may be the cause for the problem?
It does work.
Showing the log window is stunnel's way to output text messages on Windows, as there isn't necessarily a console to send the output to. (And the message box gives the 'opening credits' ;-) )
[..]
After clicking "OK" to close the popup message, I get some more info, though meaningless to me: stunnel 4.33 on x86-pc-mingw32-gnu with OpenSSL 1.0.0 29 Mar 2010 Threading:WIN32 SSL:ENGINE Sockets:SELECT,IPv6
[..]
This is the information you requested to be shown by "stunnel -version".
HTH,
Ludolf
On Fri, Aug 27, 2010 at 11:30 AM, Ludolf Holzheid [email protected] wrote:
After clicking "OK" to close the popup message, I get some more info, though meaningless to me: stunnel 4.33 on x86-pc-mingw32-gnu with OpenSSL 1.0.0 29 Mar 2010 Threading:WIN32 SSL:ENGINE Sockets:SELECT,IPv6
[..]
This is the information you requested to be shown by "stunnel -version".
Hm, but that's not very useful. I am trying to setup EMACS/Mew/stunnel for Gmail access, and Mew tries to read stunnel's version from stdout.
In fact, for a reason unclear to me, EMACS 23.1.1 hangs after executing certain ELISP code:
(call-process "stunnel" nil t nil "-version")
I see the dialog box and the main window, just as when I call stunnel from the windows command line. And of course I close these windows. Well, I guess this doesn't belong into this list.
- Felix
On Fri, 2010-08-27 11:48:17 +0000, Felix E. Klee wrote:
On Fri, Aug 27, 2010 at 11:30 AM, Ludolf Holzheid [email protected] wrote:
After clicking "OK" to close the popup message, I get some more info, though meaningless to me: stunnel 4.33 on x86-pc-mingw32-gnu with OpenSSL 1.0.0 29 Mar 2010 Threading:WIN32 SSL:ENGINE Sockets:SELECT,IPv6
[..]
This is the information you requested to be shown by "stunnel -version".
Hm, but that's not very useful. I am trying to setup EMACS/Mew/stunnel for Gmail access, and Mew tries to read stunnel's version from stdout.
Pipelining (connecting processes via stdin/stdout) seems to be very tricky on Windows.
Maybe Emacs can be fooled with a wrapper batch that outputs a version message if called with -version and calls stunnel else.
In fact, for a reason unclear to me, EMACS 23.1.1 hangs after executing certain ELISP code:
(call-process "stunnel" nil t nil "-version")
I suppose it is waiting for the started process to finish.
I see the dialog box and the main window, just as when I call stunnel from the windows command line. And of course I close these windows.
Closing the two windows does not shut down stunnel. You have to right-click on the stunnel icon in the system tray and select 'exit'.
HTH,
Ludolf
Hm, but that's not very useful. I am trying to setup EMACS/Mew/stunnel for Gmail access, and Mew tries to read stunnel's version from stdout.
Maybe Emacs can be fooled with a wrapper batch that outputs a version message if called with -version and calls stunnel else.
A good idea, thanks! However, for a first try, I slightly modified the Mew source code. It works now. But, it seems that I don't like Mew that much... ;-)
Anyway, I also had to change source code which originally added some options to the mew configuration file, and those options are not supported by stunnel for Windows:
pid foreground syslog
Would've been helpful if stunnel simply ignores these options on Windows. Instead, it displays error messages: "Specified option name is not valid here"
I see the dialog box and the main window, just as when I call stunnel from the windows command line. And of course I close these windows.
Closing the two windows does not shut down stunnel. You have to right-click on the stunnel icon in the system tray and select 'exit'.
There is no tray icon after executing "stunnel -version". I had to close it using the Windows Task Manager.
- Felix
-
Felix E. Klee -
Ludolf Holzheid