November 2007 - stunnel-users

Stunnel and Outlook Web Access Problems
by Dan Vespa 18 Nov '07

18 Nov '07

I am trying to use the latest version of stunnel to connect to OWA. I set stunnel to listen on port 80 (localhost) and then connect to myserverip on port 443. I get the login screen but can go no further after I Enter my credentials and Click OK. Checking the stunnel log screen it shows that a connect has been made? I don't understand why It won't connect any further?? OWA is on Exchange Server 2003 and I am using Windows XP SP2. I have also updated to Open SSL latest version. Thanks in Advance. Dan

2 1

NFS over stunnel
by Andy Wettstein 18 Nov '07

18 Nov '07

Hi, I wrote a document about how I am running NFS over stunnel. Using some firewall rules I was able to eliminate most of the complications for using secure NFS. It could probably use more detailed explanations, but the scripts I am using are all there. It still kind of in test phase, but I am currently mounting my home directory using stunnel. I haven't really noticed much of a speed problem in day to day activities. https://w3.physics.uiuc.edu/physwiki/doku.php?id=pcs:unix:nfs_over_stunnel Please send any questions you might have. -- andy wettstein unix administrator department of physics university of illinois at urbana-champaign

2 2

receive error
by Protect Girl 14 Nov '07

14 Nov '07

Hi When run stunnel.exe, I was receive "the procedure entry point SSL_CTX_xet_info_callback could not be located in the dynamic library libssl32.dll" error.

2 1

can't get client address
by Draeath Spamtrap 13 Nov '07

13 Nov '07

Stunnel appears to be working fine, but when started it spams my syslog about 5 times with the following message: "stunnel: warning: can't get client address: Bad file descriptor" There are no other messages from stunnel. I'm not sure where it's coming from... It looks like it is running without command line arguments. My init script has the following snippets that make me think that: > PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin > PREFIX=/usr/local > DAEMON=/usr/local/bin/stunnel > PIDFILE=/var/lib/stunnel/stunnel.pid > > test -f $DAEMON || exit 0 > > case "$1" in > start) > echo -n "Starting universal SSL tunnel: stunnel" > $DAEMON || echo -n " failed" > echo "." > ;; > {TRIMMED REST OF FILE} My stunnel version info: > stunnel 4.21 on i686-pc-linux-gnu with OpenSSL 0.9.8e 23 Feb 2007 > Threading:PTHREAD SSL:ENGINE Sockets:POLL,IPv6 Auth:LIBWRAP > > Global options > debug = 5 > pid = /usr/local/var/run/stunnel/stunnel.pid > RNDbytes = 64 > RNDfile = /dev/urandom > RNDoverwrite = yes > Service-level options > cert = /usr/local/etc/stunnel/stunnel.pem > ciphers = ALL:!ADH:+RC4:@STRENGTH > key = /usr/local/etc/stunnel/stunnel.pem > session = 300 seconds > sslVersion = SSLv3 for client, all for server > TIMEOUTbusy = 300 seconds > TIMEOUTclose = 60 seconds > TIMEOUTconnect = 10 seconds > TIMEOUTidle = 43200 seconds > verify = none My stunnel config file: > cert = /usr/local/etc/stunnel/stunnel.pem > key = /usr/local/etc/stunnel/stunnel.pem > sslVersion = SSLv3 > chroot = /var/lib/stunnel/ > setuid = 99 > setgid = 99 > pid = /stunnel.pid > socket = l:TCP_NODELAY=1 > socket = r:TCP_NODELAY=1 > client = yes > [nntps] > accept = 127.0.0.1:119 > connect = secure.news.easynews.com:563 Again, it is all working, and aside from my TCP_NODELAY flags, everything in my conf would be a show-stopper if it was invalid or not working... *of note: I had to set the uid/gid number. for some reason it couldn't resolve the gid/uid on it's own. My /etc/passwd is world-readable (with hashes in shadow) as is standard. I'm not sure I should even be worried about this...

2 2

Reporting bugs in stunnel 4.21
by Michal Trojnara 10 Nov '07

10 Nov '07

Dear Users, Please test the new stunnel 4.21 and report your issues on the Bug Tracking System (http://stunnel.mirt.net/bts.html) or email the information to the stunnel-users mailing list. This is the easiest way to help stunnel working fine on your various systems. I was developing it for quite a long time and I likely failed to fix all the bugs. I'm especially interested in all compilation or runtime issues with the new FIPS and libwrap code. By the time you can find a patch for setuid/setgid+chroot problem here: ftp://stunnel.mirt.net/stunnel/setuid.patch Best regards, Mike

2 2

How is it working?
by fuzzy_4711 06 Nov '07

06 Nov '07

Hello list. After a few tries, my stunnel configuration is working well. I am using it to tunnel my vnc connections to my winXP box. Now I have a question about how the software is working. In the past, when I was using VNC at port 5900 and I did a telnet to that box with port 5900, VNC was answering with something like 003005 which was the VNC protocol version the server was able to communicate. Now because of the tunneling effect, my vnc server still listens at 127.0.0.1:5900 but is expecting ssled connections at xxx.xxx.xxx.xxx:9999. When I do a telnet at xxx.xxx.xxx.xxx at port 9999 my box is answering something like: Connected to xxx.xxx.xxx.xxx Escape character is ... Now if enter something like "test" the telnet window shows me that the connection is closed by foreign host (means: my xp box). Lets assume, someone is trying to hack my computer and doing a port scan. She/he will find out for sure, that my port 9999 is opened. Usually the server listening behind the port is sending something the attacker could use to point to the software running behind the port. In this case, as far as I can see nothing is sent to give a hint that stunnel is waiting there to route my connection attempt to 127.0.0.1:5900. Is it right, that this is the magic - for sure besides encryption and all the algorithms necessary to do the port forwarding - stunnel provides? I mean as long as an attacker doesnt know what is hiding behind the port he/she also doesnt know how to attack or how to get through. Is that conclusion right? Please tell me, if my conclusions are wrong or if I got something wrong. Stefan

3 2

PATCH: Support PostgreSQL SSL
by Marko Kreen 06 Nov '07

06 Nov '07

PostgreSQL protocol has small handshake on connecting before SSL can be initialized. But that means that Stunnel cannot be used by default as it expects the SSL initialization to be the first thing when getting connection. Attached patch adds PostgreSQL protocol support to Stunnel, so that Stunnel can be used to provide SSL when either client or server is not able to do it natively. SSL handshake is described here: http://www.postgresql.org/docs/8.3/static/protocol-flow.html#AEN73013 Patch is tested and works, hopefully it can be included in main Stunnel source. -- marko

1 0

STUNNEL Licensing
by Menon, Sreejith Mohan 05 Nov '07

05 Nov '07

Dear Users, Is there any special licensing required to use STUNNEL ? In case, it is not required from STUNNEL , is there anything to be done on the OPENSSL side ? Thanks and best regards, Sreejith Mohan Menon

1 0

Re: [stunnel-users] almost working
by Tom Allison 05 Nov '07

05 Nov '07

Luke Deller wrote: > Hi Tom, > >> OK, this has been nothing but a bust. > > I've just read this thread, and it looks to me that you have stunnel configured incorrectly for use with inetd. > > Did you see this documentation? > http://www.stunnel.org/faq/stunnel.html#inetd_mode > >> the error keeps saying that port 993 is already in use. > > This is because you have configured stunnel to bind to port 993 using an "accept" option in the configuration file. When using stunnel with inetd, stunnel should not bind to any port; it is inetd which binds to a port. When a client connects to inetd, then inetd will launch stunnel with stunnel's stdin and stdout streams hooked up to the connected socket. > Made some progress. Got past the SSL version. Fixed my firewall to permit IMAPS sessions. confirmed my firewall settings by changing to IMAP and running directly against the imap server. Changed firewall settings from imap to imaps. Keep timing out. Same problem for Mac Mail application (which isn't great) and Debian's Icedove. This is as far as I can get. 2007.11.05 05:43:56 LOG7[27692:47518144360528]: Connection from 65.29.101.30:49841 permitted by libwrap 2007.11.05 05:43:56 LOG5[27692:47518144360528]: inetd connected from 65.29.101.30:49841 2007.11.05 05:43:56 LOG7[27692:47518144360528]: SSL state (accept): before/accept initialization 2007.11.05 05:43:56 LOG7[27692:47518144360528]: SSL state (accept): SSLv3 read client hello A 2007.11.05 05:43:56 LOG7[27692:47518144360528]: SSL state (accept): SSLv3 write server hello A 2007.11.05 05:43:56 LOG7[27692:47518144360528]: SSL state (accept): SSLv3 write certificate A 2007.11.05 05:43:56 LOG7[27692:47518144360528]: SSL state (accept): SSLv3 write server done A 2007.11.05 05:43:56 LOG7[27692:47518144360528]: SSL state (accept): SSLv3 flush data

1 0