stunnel-users

3306 discussions

stunnel and logrotate
by Bohdan Linda 06 Oct '05

06 Oct '05

Hello, I have noticed that by sending -HUP signal to stunnel causes daemon to exit. The problem is when stunnel is logging to a file and the file was recreated (i.e. by logrotate). I have blindly configured logrotate to send -HUP to the stunnel after the logs are rotated and awaited 'common-habbit' functionality: re-read configuration and refresh file handles. But I was supprised: xxxx@yyyyy:/var/log# more stunnel.log.1 2005.09.27 14:07:51 LOG5[23244:3084273344]: stunnel 4.07 on xxxxxxxxxxxxxxx 2005.09.27 14:07:51 LOG5[23244:3084273344]: 500 clients allowed 2005.10.02 04:40:03 LOG3[23245:3084273344]: Received signal 1; terminating Apparently messages are going to the 'old' filehandle and stunnel exits. Is there any workaround to this except: 1) hard restarting stunnel 2) putting stunnel in inetd Thank you, Bohdan

2 1

Stunnel 4.12 won't work with Openssl 0.98
by Luca G. 05 Oct '05

05 Oct '05

Hi I upgraded yesterday from stunnel 4.11 to 4.12, and i had a few problems... Basically I have been unable to use latest libeay32.dll and libssl32.dll versions (the one that comes with stunnel's installation file). I use stunnel to tunnel a thightvnc connection from my windows xp sp2 workstation to a couple of windows 2000 server machine on the opposite side of the building. At the moment i'm keeping 0.98 files on the server machines, 0.97f on my client and it works These are my stunnel.conf files -----------------------------------client CAfile = CAcert.pem CApath = certificates cert = client.pem client = yes verify = 3 debug = 7 output = stunnel.log [vnc] accept = 127.0.0.1:5900 connect = 192.168.1.252:443 [vnc2] accept = 127.0.0.1:5899 connect = 192.168.1.254:443 ---------------------------------------- -------------------------------server CAfile = CAcert.pem CApath = certificates cert = server.pem client = no verify = 3 debug = 7 output = stunnel.log [vnc] accept = 443 connect = 127.0.0.1:5900 -------------------------------------- And this is what i found in my log files after every connection attempt -----------------------------------client 2005.10.05 09:50:21 LOG5[3880:3960]: stunnel 4.12 on x86-pc-mingw32-gnu WIN32+SELECT+IPv6 with OpenSSL 0.9.8 05 Jul 2005 2005.10.05 09:50:21 LOG7[3880:3964]: RAND_status claims sufficient entropy for the PRNG 2005.10.05 09:50:21 LOG6[3880:3964]: PRNG seeded successfully 2005.10.05 09:50:21 LOG7[3880:3964]: Certificate: client.pem 2005.10.05 09:50:21 LOG7[3880:3964]: Key file: client.pem 2005.10.05 09:50:21 LOG7[3880:3964]: Loaded verify certificates from CAcert.pem 2005.10.05 09:50:21 LOG7[3880:3964]: Verify directory set to certificates 2005.10.05 09:50:21 LOG5[3880:3964]: Peer certificate location certificates 2005.10.05 09:50:21 LOG5[3880:3964]: No limit detected for the number of clients 2005.10.05 09:50:21 LOG7[3880:3964]: FD 164 in non-blocking mode 2005.10.05 09:50:21 LOG7[3880:3964]: SO_REUSEADDR option set on accept socket 2005.10.05 09:50:21 LOG7[3880:3964]: vnc bound to 127.0.0.1:5900 2005.10.05 09:50:21 LOG7[3880:3964]: FD 168 in non-blocking mode 2005.10.05 09:50:21 LOG7[3880:3964]: SO_REUSEADDR option set on accept socket 2005.10.05 09:50:21 LOG7[3880:3964]: vnc2 bound to 127.0.0.1:5899 2005.10.05 09:50:30 LOG7[3880:3964]: vnc accepted FD=176 from 127.0.0.1:1351 2005.10.05 09:50:30 LOG7[3880:3964]: Creating a new thread 2005.10.05 09:50:30 LOG7[3880:3964]: New thread created 2005.10.05 09:50:30 LOG7[3880:388]: vnc started 2005.10.05 09:50:30 LOG7[3880:388]: FD 176 in non-blocking mode 2005.10.05 09:50:30 LOG5[3880:388]: vnc connected from 127.0.0.1:1351 2005.10.05 09:50:30 LOG7[3880:388]: FD 200 in non-blocking mode 2005.10.05 09:50:30 LOG7[3880:388]: vnc connecting 192.168.1.252:443 2005.10.05 09:50:30 LOG7[3880:388]: connect_wait: waiting 10 seconds 2005.10.05 09:50:30 LOG7[3880:388]: connect_wait: connected 2005.10.05 09:50:30 LOG7[3880:388]: Remote FD=200 initialized 2005.10.05 09:50:30 LOG7[3880:388]: SSL state (connect): before/connect initialization 2005.10.05 09:50:30 LOG7[3880:388]: SSL state (connect): SSLv3 write client hello A 2005.10.05 09:50:30 LOG7[3880:388]: SSL state (connect): SSLv3 read server hello A 2005.10.05 09:50:30 LOG5[3880:388]: VERIFY OK: depth=1, /C=IT/ST=Trentino/L=Trento/O=ATAS onlus/OU=Atas Trento/CN=VNC/emailAddress=tecnico(a)atas.tn.it 2005.10.05 09:50:30 LOG5[3880:388]: VERIFY OK: depth=0, /C=IT/ST=Trentino/L=Trento/O=ATAS onlus/OU=Atas Trento/CN=VNC_server/emailAddress=tecnico(a)atas.tn.it 2005.10.05 09:50:30 LOG7[3880:388]: SSL state (connect): SSLv3 read server certificate A 2005.10.05 09:50:30 LOG7[3880:388]: SSL state (connect): SSLv3 read server certificate request A 2005.10.05 09:50:30 LOG7[3880:388]: SSL state (connect): SSLv3 read server done A 2005.10.05 09:50:30 LOG7[3880:388]: SSL state (connect): SSLv3 write client certificate A 2005.10.05 09:50:30 LOG7[3880:388]: SSL state (connect): SSLv3 write client key exchange A 2005.10.05 09:50:30 LOG7[3880:388]: SSL state (connect): SSLv3 write certificate verify A ----------------------------------- -----------------------------------server 2005.10.04 10:49:50 LOG5[2480:2760]: stunnel 4.12 on x86-pc-mingw32-gnu WIN32+SELECT+IPv4 with OpenSSL 0.9.8 05 Jul 2005 2005.10.04 10:49:51 LOG7[2480:2824]: RAND_status claims sufficient entropy for the PRNG 2005.10.04 10:49:51 LOG6[2480:2824]: PRNG seeded successfully 2005.10.04 10:49:51 LOG7[2480:2824]: Certificate: server.pem 2005.10.04 10:49:51 LOG7[2480:2824]: Key file: server.pem 2005.10.04 10:49:51 LOG7[2480:2824]: Loaded verify certificates from CAcert.pem 2005.10.04 10:49:51 LOG7[2480:2824]: Verify directory set to certificates 2005.10.04 10:49:51 LOG5[2480:2824]: Peer certificate location certificates 2005.10.04 10:49:51 LOG5[2480:2824]: No limit detected for the number of clients 2005.10.04 10:49:51 LOG7[2480:2824]: FD 864 in non-blocking mode 2005.10.04 10:49:51 LOG7[2480:2824]: SO_REUSEADDR option set on accept socket 2005.10.04 10:49:51 LOG7[2480:2824]: vnc bound to 0.0.0.0:443 2005.10.04 10:51:00 LOG7[2480:2824]: vnc accepted FD=852 from 192.168.1.250:13545 2005.10.04 10:51:00 LOG7[2480:2824]: Creating a new thread 2005.10.04 10:51:00 LOG7[2480:2824]: New thread created 2005.10.04 10:51:00 LOG7[2480:2740]: vnc started 2005.10.04 10:51:00 LOG7[2480:2740]: FD 852 in non-blocking mode 2005.10.04 10:51:00 LOG5[2480:2740]: vnc connected from 192.168.1.250:13545 2005.10.04 10:51:00 LOG7[2480:2740]: SSL state (accept): before/accept initialization 2005.10.04 10:51:00 LOG7[2480:2740]: SSL state (accept): SSLv3 read client hello A 2005.10.04 10:51:00 LOG7[2480:2740]: SSL state (accept): SSLv3 write server hello A 2005.10.04 10:51:00 LOG7[2480:2740]: SSL state (accept): SSLv3 write certificate A 2005.10.04 10:51:00 LOG7[2480:2740]: SSL state (accept): SSLv3 write certificate request A 2005.10.04 10:51:00 LOG7[2480:2740]: SSL state (accept): SSLv3 flush data 2005.10.04 10:51:00 LOG3[2480:2740]: SSL_accept: Peer suddenly disconnected 2005.10.04 10:51:00 LOG7[2480:2740]: vnc finished (0 left) ----------------------------------- Am i doing soething wrong? Thanks in advance Luca

1 0

4.12 Broken?
by G J Piper 04 Oct '05

04 Oct '05

The new Stunnel Version 4.12 doesn't work well with POPs mail retrieval on my system. Reverting back to 4.11 fixes it perfectly. With 4.12, various emails wouldn't come through, got random timeouts, LONG email retrieval times mainly. Sometimes an email would be impossible to retrieve from the spool file. Running Stunnel with default parameters. Standalone I believe POPs runs off xinetd. % uname -a FreeBSD pipercomputerservices.net 4.4-RELEASE FreeBSD 4.4-RELEASE #0: Wed Aug 28 19:41:18 GMT 2002 root@osbuilder:/usr/src/sys/compile/SERVER i386 % gcc -v Using builtin specs. gcc version 2.95.3 20010315 (release) [FreeBSD] % openssl version OpenSSL 0.9.6e 30 Jul 2002 % stunnel -version stunnel 4.11 on i386-unknown-freebsd4.4 PTHREAD+POLL+IPv4+LIBWRAP with OpenSSL 0.9.6e 30 Jul 2002 Global options cert = /usr/local/etc/stunnel/stunnel.pem ciphers = ALL:!ADH:+RC4:@STRENGTH debug = 5 key = /usr/local/etc/stunnel/stunnel.pem pid = /usr/local/var/run/stunnel.pid RNDbytes = 64 RNDfile = /dev/urandom RNDoverwrite = yes session = 300 seconds verify = none Service-level options TIMEOUTbusy = 300 seconds TIMEOUTclose = 60 seconds TIMEOUTconnect = 10 seconds TIMEOUTidle = 43200 seconds

2 2

Help: Remote desktop connection crashes Stunnel
by Jonathan Bell 04 Oct '05

04 Oct '05

In an attempt to get remote desktop set up over SSL tunneling with compression, I have installed stunnel on my Windows XP Professional SP2 machine and created a "portable" stunnel/config/dll zip that just contains the essentials to create a pre-configured tunnel. Here are the two config files: Server -------------------------------- ; Sample stunnel configuration file by Michal Trojnara 2002-2005 ; Some options used here may not be adequate for your particular configuration ; Certificate/key is needed in server mode and optional in client mode ; The default certificate is provided only for testing and should not ; be used in a production environment cert = stunnel.pem key = stunnel.pem ; Some performance tunings socket = l:TCP_NODELAY=1 socket = r:TCP_NODELAY=1 compression = zlib ; Some debugging stuff useful for troubleshooting debug = 6 output = G:\Stunnel Logs\stunnel.log taskbar = no ; Use it for client mode client = no ; Service-level configuration [remote-desktop] accept = 9833 connect = 127.0.0.1:3389 --------------------------------- Client --------------------------------- ; Sample stunnel configuration file by Michal Trojnara 2002-2005 ; Some options used here may not be adequate for your particular configuration ; Some performance tunings socket = l:TCP_NODELAY=1 socket = r:TCP_NODELAY=1 compression = zlib ; Some debugging stuff useful for troubleshooting debug = 7 output = stunnel.log taskbar = yes ; Use it for client mode client = yes ; Service-level configuration [remote-desktop] accept = 127.0.0.1:6389 connect = my.host.name:9833 ---------------------------------- The procedure I used was as follows - start Stunnel on the host, run upstairs with the zipped "portable" stunnel on a USB drive, run stunnel on the other PC, also running XP Pro SP2. Start->run->mstsc, enter 127.0.0.1:6389 and all that happens is that stunnel instantly crashes then Remote Desktop times out. What am I doing wrong?

2 1

Dual Instance of Stunnel Service on W2K
by Mundy Jennifer 04 Oct '05

04 Oct '05

Am new to stunnel and in need of some help. I have W2K box that has Stunnel installed as a service. Upon startup, it starts the service and uses the default stunnel.conf file. I would like to install a second Stunnel service and call a custom .conf service. Is this possible? I've read thru the documentation but haven't come across anything about a second service. We're running v4.05. I know I can get a second instance running via cmd line/batch file, but need the second instance to startup automatically so it can be monitored as well as other things. Thank you in advance. Jennifer The information contained in this e-mail may be confidential and is intended solely for the use of the named addressee. Access, copying or re-use of the e-mail or any information contained therein by any other person is not authorized. If you are not the intended recipient please notify us immediately by returning the e-mail to the originator.(17b)

1 0

SSL_GET_NEW_SESSION:ssl session id callback failed
by DoJo 04 Oct '05

04 Oct '05

Hi There, We have run into "SSL_GET_NEW_SESSION:ssl session id callback failed" error. Can anyone describe what it means? I didn't find any information about it. We'd like to use stunnel to secure Oracle SQL*Net communication. HP-UX server communicates with Win32 clients. We use stunnel standalone not from inetd. Any help would be appreciated. Thanks DoJo Here is a cut from the log file (level 7): 2005.09.29 11:49:53 LOG5[10388:1]: stunnel 4.09 on hppa2.0w-hp-hpux11.11 PTHREAD+POLL+IPv4+LIBWRAP with OpenSSL 0.9.7e 25 Oct 2004 2005.09.29 11:49:53 LOG7[10388:1]: Snagged 0 random bytes from EGD Socket /var/run/egd-pool 2005.09.29 11:49:53 LOG6[10388:1]: PRNG seeded successfully 2005.09.29 11:49:53 LOG7[10388:1]: Certificate: /opt/iexpress/stunnel/etc/stunnel/..._cert.cer 2005.09.29 11:49:53 LOG7[10388:1]: Key file: /opt/iexpress/stunnel/etc/stunnel/..._privkey.pem 2005.09.29 11:49:53 LOG6[10388:1]: file ulimit = 60 (can be changed with 'ulimit -n') 2005.09.29 11:49:53 LOG6[10388:1]: poll() used - no FD_SETSIZE limit for file descriptors 2005.09.29 11:49:53 LOG5[10388:1]: 27 clients allowed 2005.09.29 11:49:53 LOG7[10388:1]: FD 4 in non-blocking mode 2005.09.29 11:49:53 LOG7[10388:1]: FD 5 in non-blocking mode 2005.09.29 11:49:53 LOG7[10388:1]: FD 6 in non-blocking mode 2005.09.29 11:49:53 LOG7[10388:1]: SO_REUSEADDR option set on accept socket 2005.09.29 11:49:53 LOG7[10388:1]: myapp bound to 0.0.0.0:2000 2005.09.29 11:49:53 LOG7[10389:1]: Created pid file /stunnel.pid 2005.09.30 12:01:47 LOG7[10389:1]: myapp accepted FD=1 from 10.3.125.165:3570 2005.09.30 12:01:47 LOG7[10389:1]: FD 1 in non-blocking mode 2005.09.30 12:01:47 LOG7[10389:2]: myapp started 2005.09.30 12:01:47 LOG5[10389:2]: myapp connected from 10.3.125.165:3570 2005.09.30 12:01:47 LOG7[10389:2]: SSL state (accept): before/accept initialization 2005.09.30 12:01:47 LOG3[10389:2]: SSL_accept: 140B544E: error:140B544E:SSL routines:SSL_GET_NEW_SESSION:ssl session id callback failed 2005.09.30 12:01:47 LOG7[10389:2]: myapp finished (0 left) Our config file: cert = /opt/iexpress/stunnel/etc/stunnel/..._cert.cer # contains the server's signed (by a CA) cert. key = /opt/iexpress/stunnel/etc/stunnel/..._privkey.pem # contains the server's private key service = myapp-ssl chroot = /var/run/stunnel pid = /stunnel.pid setuid = oracle setgid = oracle debug = 7 output = stunnel.log client = no [myapp] accept=2000 connect=1521

1 1

stunnel4 user + permissions
by nick.hoffman＠altcall.com 04 Oct '05

04 Oct '05

Hey guys, I've been using stunnel for a while and it's great. I've noticed something that doesn't make much sense to me though, so I was wondering if you might be able to shed some light. Stunnel runs as user:group stunnel4:stunnel4. The server reads client certs (for verify = 3) from /etc/stunnel/certs/ which is chown'd root:ssl-certs and chmod'd 750. The client PEMs in that directory have the same ownership and permissions. User stunnel4 is in the ssl-certs group. When a client connects, the server is unable to read from /etc/stunnel/certs/. If I change the ownership of the directory to root:stunnel4 though, everything works. Any idea why this occurs? Cheers, Nick

2 1

Win2k, stunnel & Magic Mail Monitor questions
by Dana Rasmussen 04 Oct '05

04 Oct '05

Hello, I am running Windows 2000. I have recently learned of the stunnel tool. I am using it with Magic Mail Monitor, (MMM). MMM is a POP3 new mail notifier program. MMM allows me to configure a POP3 server by user name, host, password and POP3 port. MMM allows me to have multiple POP3 servers configured. Unfortunately, MMM does not use SSL. I have been able to get MMM to work with stunnel with the following stunnel.conf file: client = yes [MyPOP3SSL] accept=995 connect=mypop3server.com:995 The associated MMM configuration is: user: myuser host: 127.0.0.1 password:mypassword port:995 I would like to be able to add a second POP3 server to MMM, i.e. Gmail. If I add the following to the bottom of the existing stunnel.conf file Gmail POP3SSL access fails. If I add the following to the top of the existing stunnel.conf file the MyPOP3SSL fails but Gmail works. [GmailPOP3SSL] accept=995 connect=pop.gmail.com:995 The additional MMM configuration is: user:mygmail host: 127.0.0.1 password:mygmailpassword port:995 Is there a way to map the MMM configurations to the matching entries in the stunnel.conf file? Thank you, Dana

2 1

Peer suddenly disconnected
by Mark Tabash 03 Oct '05

03 Oct '05

Hello, I'm having problems using stunnel. I would be glad to provide further information upon request. The funny thing is that it was working before I shipped the client pc to the remote location. Nothing has changed since. Here's what I get in the logs: CLIENT: ssmtp accepted FD=8 from 127.0.0.1:32844 FD 8 in non-blocking mode ssmtp started ssmtp connected from 127.0.0.1:32844 FD 9 in non-blocking mode ssmtp connecting 62.21.201.224:465 remote connect #1: EINPROGRESS: retrying waitforsocket: FD=9, DIR=write waitforsocket: ok Remote FD=9 initialized SSL state (connect): before/connect initialization SSL state (connect): SSLv3 write client hello A waitforsocket: FD=9, DIR=read waitforsocket: ok SSL state (connect): SSLv3 read server hello A SSL state (connect): SSLv3 read server certificate A SSL state (connect): SSLv3 read server certificate request A SSL state (connect): SSLv3 read server done A SSL state (connect): SSLv3 write client certificate A SSL state (connect): SSLv3 write client key exchange A SSL state (connect): SSLv3 write certificate verify A SSL state (connect): SSLv3 write change cipher spec A SSL state (connect): SSLv3 write finished A SSL state (connect): SSLv3 flush data waitforsocket: FD=9, DIR=read waitforsocket: ok SSL_connect: Peer suddenly disconnected ssmtp finished (0 left) SERVER: ssmtp accepted FD=8 from 77.34.26.143:32845 FD 8 in non-blocking mode ssmtp started ssmtp connected from 77.34.26.143:32845 SSL state (accept): before/accept initialization SSL state (accept): SSLv3 read client hello A SSL state (accept): SSLv3 write server hello A SSL state (accept): SSLv3 write certificate A SSL state (accept): SSLv3 write certificate request A SSL state (accept): SSLv3 flush data SSL_accept: Peer suddenly disconnected ssmtp finished (0 left) ============================================ CLIENT INFO: stunnel 4.05 on i386-pc-linux-gnu PTHREAD+LIBWRAP with OpenSSL 0.9.7e 25 Oct 2004 Global options cert = /etc/stunnel/stunnel.pem ciphers = ALL:!ADH:+RC4:@STRENGTH debug = 5 key = /etc/stunnel/stunnel.pem pid = /var/run/stunnel4/stunnel.pid RNDbytes = 64 RNDfile = /dev/urandom RNDoverwrite = yes session = 300 seconds verify = none Service-level options TIMEOUTbusy = 300 seconds TIMEOUTclose = 60 seconds TIMEOUTidle = 43200 seconds ------------------ SERVER INFO: stunnel 4.09 on x86_64-pc-linux-gnu PTHREAD+POLL+IPv6+LIBWRAP with OpenSSL 0.9.7e 25 Oct 2004 Global options cert = /etc/stunnel/stunnel.pem ciphers = ALL:!ADH:+RC4:@STRENGTH debug = 5 key = /etc/stunnel/stunnel.pem pid = /var/lib/run/stunnel.pid RNDbytes = 64 RNDfile = /dev/urandom RNDoverwrite = yes session = 300 seconds verify = none Service-level options TIMEOUTbusy = 300 seconds TIMEOUTclose = 60 seconds TIMEOUTconnect = 10 seconds TIMEOUTidle = 43200 seconds

2 2

Stunnel 4.12 released
by Michal Trojnara 30 Sep '05

30 Sep '05

Here is the ChangeLog entry: Version 4.12, 2005.09.29, urgency: MEDIUM: * New features - Win32 installer added. - New Win32 commandline options: -start and -stop. - Log level and thread number are reported to syslog. - DLLs for OpenSSL 0.9.8. - stunnel.spec updated by neeo <neeo(a)irc.pl>. * Bugfixes - Use of broken poll() is disabled on Mac OS X. - Yet another transfer() infinite loop condition fixed. - Workaround for a serious M$ bug (KB177346). - IPv6 DLLs allocation problem resulting in GPF on W2K fixed. - zlib added to shared libraries (OpenSSL may need it). - size_t printf() fixed in stack_info(). * Release notes - This is a bugfix release. Upgrade is recommended. Homepage: http://stunnel.mirt.net/ Download: ftp://stunnel.mirt.net/stunnel/ sha1sum: 3a0f1b9955f64dcab376b4145663f1eadc5dfba5 stunnel-4.12.tar.gz Best regards, Mike

2 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

stunnel-users