- stunnel-users - stunnel.org

Installing Stunnel 4.21 on Shared Hosting Server with OpenSSL 0.9.6g
by Norbert Hoeller 17 Feb '08

17 Feb '08

I am trying to install Stunnel 4.21 on a 1&1 shared Linux server. PHP Settings claims that OpenSSL 0.9.6g is installed. I unpacked the tar file and ran "./configure" using --prefix to override the /usr/local/ install directory. I had one warning: "configure: WARNING: Openssl engine header not found". In terms of threading model, I got "configure: PTHREAD thread model detected". When I tried to run "make", I got "common.h:318: #error OpenSSL library compiled without thread support". Is there a way around this? I tried running "./configure" with --with-threads=ucontext/fork, but that gave a bunch of "OCSP_" undeclared variables and "Error 1". Thanks, Norbert

2 2

Validation of certificate
by Edouard Dessioux 12 Feb '08

12 Feb '08

Hi everyone, I'm new to this mailing list, but before my asking question, i checked the archive but did not find anything related, so, it may be out of topic. Well, for the moment, I can't provide all the informations asked like « output of ... command », but I'm not sure this is relevant for my question. The informations I can provide are : * I use stunnel to terminate a tls connection between a mobile phone and a web application server. * I use stunnel to validate my clients certificates. * The stunnel will be running on a windows 2003 server * I guess I would be using the last available version of stunnel * The certificates would be generated by a PKI different from openssl What I would like to do is : I have a PKI already deployed with many certificates, and I want only a small subset of them to be validated by the stunnel. I thought of using multiples OU fields to « tags » some users, but can this fields be checked by stunnel ? Do you guys have any feedback on this or any alternative way to do something equivalent ? Regards, Edouard DESSIOUX Directeur de Projets Tibco Mobile 3, rue Danton - 92240 Malakoff Tél : +33 (0)1 55 58 04 59 - Fax : +33 (0)1 55 58 03 89 - Mob. +33 (0)6 34 02 61 54 E-mail : edessioux(a)tibco.fr - www.tibcomobile.fr Faites un geste pour la planète, n'imprimez ce message que si nécessaire.

1 0

signal 15 terminating stunnel on start in Ubuntu
by Rick Barry 11 Feb '08

11 Feb '08

I am trying to use Stunnel 4.2 on Ubuntu 7.1. When I use this command to start Stunnel: /etc/init.d/stunnel4 start I get this output: Starting SSL tunnels: 2008.02.11 09:00:05 LOG7[6780:3082872496]: RAND_status claims sufficient entropy for the PRNG 2008.02.11 09:00:05 LOG7[6780:3082872496]: PRNG seeded successfully 2008.02.11 09:00:05 LOG7[6780:3082872496]: SSL context initialized for service nntp [Failed: /etc/stunnel/stunnel.conf] You should check that you have specified the pid= in you configuration file In the log entry @ /var/log/stunnel4/stunnel.log: 2008.02.11 08:33:54 LOG5[5468:3082974896]: stunnel 4.20 on i486-pc-linux- gnu with OpenSSL 0.9.8e 23 Feb 2007 2008.02.11 08:33:54 LOG5[5468:3082974896]: ThreadingTHREAD SSL:ENGINE SocketsOLL,IPv6 Auth:LIBWRAP 2008.02.11 08:33:54 LOG6[5468:3082974896]: file ulimit = 1024 (can be changed with 'ulimit -n') 2008.02.11 08:33:54 LOG6[5468:3082974896]: poll() used - no FD_SETSIZE limit for file descriptors 2008.02.11 08:33:54 LOG5[5468:3082974896]: 500 clients allowed 2008.02.11 08:33:54 LOG7[5468:3082974896]: FD 4 in non-blocking mode 2008.02.11 08:33:54 LOG7[5468:3082974896]: FD 5 in non-blocking mode 2008.02.11 08:33:54 LOG7[5468:3082974896]: FD 6 in non-blocking mode 2008.02.11 08:33:54 LOG7[5468:3082974896]: SO_REUSEADDR option set on accept socket 2008.02.11 08:33:54 LOG7[5468:3082974896]: nntp bound to 127.0.0.1:119 2008.02.11 08:33:54 LOG7[5517:3082974896]: Created pid file /stunnel4.pid 2008.02.11 08:39:10 LOG5[5517:3082974896]: Received signal 15; terminating 2008.02.11 08:39:10 LOG7[5517:3082974896]: removing pid file /stunnel4.pid Signal 15 seems to be the linchpin here, but my research hasn't brought up anything conclusive. Any pointers? Thank you. Rick Barry ____________________________________________________________________________________ Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping

1 0

Stunnel Problem - 935 Maximum connections on Windows
by Iain ＠ Mobile777 11 Feb '08

11 Feb '08

We are having some difficulties when using Stunnel under load. The maximum sessions running on a Windows servers seems to be set at 935 concurrent connections. Our system uses Stunnel to route incoming SSL traffic on port 443 through Openssl to a Java application on port 26789. Both Stunnel and the Java server run on a Windows 2003 server, with between 4GB and 8GB of ram, both running Dual Intel Zeon 2Ghz processors. The problem is that when the Stunnel server is under load, the maximum connections that we can achieve is 935 concurrent connections (Windows threads between 936 and 938), before Stunnel throws errors and starts closing the connections. Here is some additional information about our system: Stunnel version 4.21 (latest Windows binaries) OpenSSL 0.9.8g Stunnel Config: ----------------------------------------------------------------------- debug = 7 output = stunnel.log # Use it for client mode #client = yes #TIMEOUTidle = 60 socket = a:TCP_NODELAY=1 socket = a:SO_LINGER=a:0 socket = r:TCP_NODELAY=1 socket = r:SO_LINGER=r:0 socket = l:TCP_NODELAY=1 socket = l:SO_LINGER=l:0 # Service-level configuration [JAVASERVER] #session = 5000 accept = 443 connect = localhost: 26789 # delay = yes #transparent = yes ----------------------------------------------------------------------- We have tried various options, such as the TIMEOUTidle and session parameters for Stunnel, but with no luck. We have even tried running Stunnel separately on a Linux distro (FC4), with even less positive results. The pertinent errors in the log files are as follows: Connection closed: 178664 bytes sent to SSL, 44646 bytes sent to socket SSL alert (write): warning: close notify _beginthread: Exec format error (8) Connection rejected: create_client failed I can mail full logs of our load tests as well. Our server will be expected to handle upwards of 10000 connections at a time, we've been researching for about a week now how to get the performance we need, but so far nothing. Iain

3 3

Stunnel + Hybrid-ircd issues
by Strykar 09 Feb '08

09 Feb '08

Hi, I'm running Hybrid-7.2 on two PCs, one of which has a dynamic IP, as Hybrid wants a static IP and not hostname in its connect section, we are trying to use stunnel to encrypt server<->server communication. Server 1 specs (To which I'm connecting) running FreeBSD 6.3: *********************************************** #stunnel -version stunnel 4.05 on amd64-unknown-freebsd5.3 PTHREAD+LIBWRAP with OpenSSL 0.9.7e 25 Oct 2004 Global options cert = /usr/local/etc/stunnel/stunnel.pem ciphers = ALL:!ADH:+RC4:@STRENGTH debug = 5 key = /usr/local/etc/stunnel/stunnel.pem pid = /var/tmp/stunnel.pid RNDbytes = 64 RNDfile = /dev/urandom RNDoverwrite = yes #gcc -v Using built-in specs. Configured with: FreeBSD/amd64 system compiler Thread model: posix gcc version 3.4.6 [FreeBSD] 20060305 #uname FreeBSD 6.3-STABLE FreeBSD 6.3-STABLE #6: Tue Jan 22 13:23:51 GMT 2008 root@:/usr/obj/usr/src/sys/SVR1 amd64 Server 2 specs (From which I'm connecting via stunnel as a client) running OpenBSD 4.2: ****************************************************************** #stunnel -version stunnel 4.20 on i386-unknown-openbsd4.2 with OpenSSL 0.9.7j 04 May 2006 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/arandom RNDoverwrite = yes Service-level options cert = /etc/stunnel/stunnel.pem ciphers = ALL:!ADH:+RC4:@STRENGTH key = /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 # gcc -v Reading specs from /usr/lib/gcc-lib/i386-unknown-openbsd4.2/3.3.5/specs Configured with: Thread model: single gcc version 3.3.5 (propolice) # cat stunnel.conf: cert = /etc/ssl/private/stunnel.pem key = /etc/ssl/private/rsa.key setuid = _stunnel setgid = _stunnel pid = /var/run/stunnel.pid socket = l:TCP_NODELAY=1 socket = r:TCP_NODELAY=1 debug = 7 foreground = yes [irc] client = yes accept = localhost:994 connect = xxx.xxx.xxx.xxx:994 Here's the debug logged to stderr: # stunnel 2008.02.08 19:34:54 LOG7[11904:2237644800]: Snagged 64 random bytes from /dev/arandom 2008.02.08 19:34:54 LOG7[11904:2237644800]: RAND_status claims sufficient entropy for the PRNG 2008.02.08 19:34:54 LOG7[11904:2237644800]: PRNG seeded successfully 2008.02.08 19:34:54 LOG7[11904:2237644800]: Certificate: /etc/ssl/private/stunnel.pem 2008.02.08 19:34:54 LOG7[11904:2237644800]: Certificate loaded 2008.02.08 19:34:54 LOG7[11904:2237644800]: Key file: /etc/ssl/private/rsa.key 2008.02.08 19:34:54 LOG7[11904:2237644800]: Private key loaded 2008.02.08 19:34:54 LOG7[11904:2237644800]: SSL context initialized for service irc 2008.02.08 19:34:54 LOG5[11904:2237644800]: stunnel 4.20 on i386-unknown-openbsd4.2 with OpenSSL 0.9.7j 04 May 2006 2008.02.08 19:34:54 LOG5[11904:2237644800]: Threading:PTHREAD SSL:ENGINE Sockets:POLL,IPv6 Auth:LIBWRAP 2008.02.08 19:34:54 LOG6[11904:2237644800]: file ulimit = 128 (can be changed with 'ulimit -n') 2008.02.08 19:34:54 LOG6[11904:2237644800]: poll() used - no FD_SETSIZE limit for file descriptors 2008.02.08 19:34:54 LOG5[11904:2237644800]: 61 clients allowed 2008.02.08 19:34:54 LOG7[11904:2237644800]: FD 6 in non-blocking mode 2008.02.08 19:34:54 LOG7[11904:2237644800]: FD 7 in non-blocking mode 2008.02.08 19:34:54 LOG7[11904:2237644800]: FD 8 in non-blocking mode 2008.02.08 19:34:54 LOG7[11904:2237644800]: SO_REUSEADDR option set on accept socket 2008.02.08 19:34:54 LOG7[11904:2237644800]: irc bound to 127.0.0.1:994 2008.02.08 19:34:54 LOG7[11904:2237644800]: Created pid file /var/run/stunnel.pid 2008.02.08 19:35:15 LOG7[11904:2237644800]: irc accepted FD=9 from 127.0.0.1:8579 2008.02.08 19:35:15 LOG7[11904:2336256000]: irc started 2008.02.08 19:35:15 LOG7[11904:2336256000]: FD 9 in non-blocking mode 2008.02.08 19:35:15 LOG7[11904:2336256000]: TCP_NODELAY option set on local socket 2008.02.08 19:35:15 LOG7[11904:2336256000]: FD 10 in non-blocking mode 2008.02.08 19:35:15 LOG7[11904:2336256000]: FD 11 in non-blocking mode 2008.02.08 19:35:15 LOG7[11904:2336256000]: Connection from 127.0.0.1:8579 permitted by libwrap 2008.02.08 19:35:15 LOG5[11904:2336256000]: irc accepted connection from 127.0.0.1:8579 2008.02.08 19:35:15 LOG7[11904:2336256000]: FD 10 in non-blocking mode 2008.02.08 19:35:15 LOG7[11904:2336256000]: irc connecting 69.50.175.50:994 2008.02.08 19:35:15 LOG7[11904:2336256000]: connect_wait: waiting 10 seconds 2008.02.08 19:35:15 LOG7[11904:2237644800]: Cleaning up the signal pipe 2008.02.08 19:35:15 LOG6[11904:2237644800]: Child process 26562 finished with code 0 2008.02.08 19:35:15 LOG7[11904:2336256000]: connect_wait: connected 2008.02.08 19:35:15 LOG5[11904:2336256000]: irc connected remote server from 192.168.1.101:42954 2008.02.08 19:35:15 LOG7[11904:2336256000]: Remote FD=10 initialized 2008.02.08 19:35:15 LOG7[11904:2336256000]: TCP_NODELAY option set on remote socket 2008.02.08 19:35:15 LOG7[11904:2336256000]: SSL state (connect): before/connect initialization 2008.02.08 19:35:15 LOG7[11904:2336256000]: SSL state (connect): SSLv3 write client hello A 2008.02.08 19:35:15 LOG7[11904:2336256000]: SSL state (connect): SSLv3 read server hello A 2008.02.08 19:35:15 LOG7[11904:2336256000]: SSL state (connect): SSLv3 read server certificate A 2008.02.08 19:35:15 LOG7[11904:2336256000]: SSL state (connect): SSLv3 read server done A 2008.02.08 19:35:15 LOG7[11904:2336256000]: SSL state (connect): SSLv3 write client key exchange A 2008.02.08 19:35:15 LOG7[11904:2336256000]: SSL state (connect): SSLv3 write change cipher spec A 2008.02.08 19:35:15 LOG7[11904:2336256000]: SSL state (connect): SSLv3 write finished A 2008.02.08 19:35:15 LOG7[11904:2336256000]: SSL state (connect): SSLv3 flush data 2008.02.08 19:35:15 LOG7[11904:2336256000]: SSL state (connect): SSLv3 read finished A 2008.02.08 19:35:15 LOG7[11904:2336256000]: 1 items in the session cache 2008.02.08 19:35:15 LOG7[11904:2336256000]: 1 client connects (SSL_connect()) 2008.02.08 19:35:15 LOG7[11904:2336256000]: 1 client connects that finished 2008.02.08 19:35:15 LOG7[11904:2336256000]: 0 client renegotiations requested 2008.02.08 19:35:15 LOG7[11904:2336256000]: 0 server connects (SSL_accept()) 2008.02.08 19:35:15 LOG7[11904:2336256000]: 0 server connects that finished 2008.02.08 19:35:15 LOG7[11904:2336256000]: 0 server renegotiations requested 2008.02.08 19:35:15 LOG7[11904:2336256000]: 0 session cache hits 2008.02.08 19:35:15 LOG7[11904:2336256000]: 0 session cache misses 2008.02.08 19:35:15 LOG7[11904:2336256000]: 0 session cache timeouts 2008.02.08 19:35:15 LOG6[11904:2336256000]: SSL connected: new session negotiated 2008.02.08 19:35:15 LOG6[11904:2336256000]: Negotiated ciphers: AES256-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA1 2008.02.08 19:35:15 LOG3[11904:2336256000]: SSL_read: Connection reset by peer (54) 2008.02.08 19:35:15 LOG5[11904:2336256000]: Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket 2008.02.08 19:35:15 LOG7[11904:2336256000]: irc finished (0 left) What is going on here with "SSL_read: Connection reset by peer (54)"? This process keeps repeating itself without the ircd's linking. - S

1 0

Verify Question
by Vlad 08 Feb '08

08 Feb '08

I'm sure that people have asked this question before, but i cannot find a way to search the archives. What is the difference between verify = 2 and verify = 3, The docs indicate that with verify = 3it will check against locally installed certs, but what does that mean, if I use =2 then what does it verify the cert against? Also a second question: I'm pretty sure that the answer is no but is it possible to do the following, have a cert A that is signed by CA cert B which itself is singed by a self-signed cert C. If the clients has C installed as a trusted cert, and it received A, is there anyway for it to validate A. I realize that these are probably pretty novice questions so I really appreciate your patience, thanks!

1 0

xforwardedfor in config
by Jill Rochelle 04 Feb '08

04 Feb '08

I am new to stunnel and the ssl world. I'm trying to get stunnel to work with haproxy for load balancing https requests. In the haproxy documentation it says that the stunnel.conf should look like this cert=/etc/stunnel/stunnel.pem setuid=stunnel setgid=proxy socket=l:TCP_NODELAY=1 socket=r:TCP_NODELAY=1 [https] accept=192.168.1.1:443 connect=192.168.1.1:80 xforwardedfor=yes However, when I try to start the stunnel service I get this Starting stunnel: file /etc/stunnel/stunnel.conf line 9: Specified option name is not valid here If I comment out the xforwardedfor parameter, it starts. Any help is greatly appreciated. Thank you, Jill Rochelle

2 2

2 secure sockets TCP (Server / Client) as posted earlier last month by khaled
by Dick van Fulpen 04 Feb '08

04 Feb '08

> Hi, > > I'm having the same question (and problem) as posted by khaled on Mon > Jan 7 19:31:03 CET 2008, subject [stunnel-users] 2 secure sockets TCP > (Server / Client). > > I think I have to send data to stunnel on the client side by a write > to localhost:1974 where stunnel is configured with this stunnel.conf: > ; Sample stunnel configuration file by Michal Trojnara 2002-2006 > ; 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 > > ; Use it for client mode > ;client = yes > > ; Service-level configuration > [sip2s] > accept = 1975 > connect = 127.0.0.1:1974 > > To start stunnel only works with just stunnel. > Started from batch or in dos-box with the options -d -r etc. as > explained in the documentation does not work, error message: file not > found) > BTW: I'm using Windows XP Professional on both client and server. > Client IP = 10.4.208.159, server IP = 10.4.208.102 for a test set-up. > > On the server side it gives the same error when started with options. > stunnel.conf on the server is this: > ; Sample stunnel configuration file by Michal Trojnara 2002-2006 > ; 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 > > ; Some debugging stuff useful for troubleshooting > debug = 7 > output = stunnel.log > > ; Use it for client mode > client = yes > > ; Service-level configuration > [sip2s] > accept = 1975 > connect = 127.0.0.1:1974 > > Reading data on TCP/IP 1974 does not display anything when the client > is sending data to localhost:1974 which is encrypted by stunnel an > forwarded on TCP/IP 1975. > At least that is my intention, but something I do is wrong. > Data sending unencrypted between client an server works fine, so > connection is possible. > > Any idea what I should do to let it work like this: > - a client sends data to a server and reads the response from this > server. > - all data on the network between client an server should be > encrypted. > As far as I could find in the stunnel manual it should be able to use > stunnel for this. > In the manual is an example using foo (client) and bar (server). > > Dick van Fulpen | Senior Software Engineer | Infor | Tel:+31 (0)73 > 6205 222 | Dick.vanFulpen(a)infor.com | Infor | Postbus 2067 | 5202 CB > 's-Hertogenbosch | Nederland | Bezoek onze website www.vubis-smart.com > | >

1 0

Connection Refused locally, SSL Proxy.
by Avner Peled 01 Feb '08

01 Feb '08

Hello! I have a game client connecting to a server using TCP over SSL. I'm trying to setup an SSL proxy using 2 stunnels on the same server like so: Client --> Stunnel-Server:20001 (decrypt)--> Stunnel-Client:901 (encrypt)---> Server:20001 Using latest stunnel-4.21-r1 on Gentoo kernel 2.6.22-gentoo-r9 I have a weird problem. The first connection after starting both stunnels works fine. Afterwards every time the client tries to connect, it gets refused once. Then it tries again and gets connected. Then the next time it will once again get refused once and then connect. I have looked at the logs and it seems the Stunnel server (the first) gets Connection Refused from localhost:901. Then it tries again and gets connected. The Stunnel client (the second) doesn't even mention the first failing local connection in the log. I have provided the config files of both stunnels and a log with debug = 7 (server ip's are censored) I have also tried the following config tweaks with no luck socket = l:TCP_NODELAY=1 socket = r:TCP_NODELAY=1 TIMEOUTclose = 0 retry = yes Any help would be appreciated. Thanks!! -- Avner Peled. avnerus(a)gmail.com

1 1

debug level 7
by Damian Wiest 25 Jan '08

25 Jan '08

Hi, I'm new to stunnel and have run into some unexpected behavior. I'm inclined to think it's a bug, but perhaps I'm misunderstanding some things. I'm running FreeBSD 6.2 with stunnel 4.21 (installed via ports collection). I'm able to configure things properly when using stunnel in daemon mode, but am unable to run stunnel from inetd when I set the debug level to 7. Here's the config file I'm using, cert = /usr/local/CA/stunnel.pem key = /usr/local/CA/stunnel.pem sslVersion = all pid = /var/log/swat-stunnel.pid debug = 7 output = /tmp/stunnel.log exec = /usr/local/sbin/swat execargs = swat ...and the inetd.conf entry, swat stream tcp nowait.400 root /usr/local/sbin/stunnel stunnel /usr/local/etc/stunnel/swat.conf If I connect to port 901, some debug messages are written to the socket, dwiest(a)dfwdamian.vail: telnet localhost 901 Trying ::1... telnet: connect to address ::1: Connection refused Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 2008.01.22 22:19:09 LOG7[81278:134651904]: Snagged 64 random bytes from /home/dwiest/.rnd 2008.01.22 22:19:09 LOG7[81278:134651904]: Wrote 1024 new random bytes to /home/dwiest/.rnd 2008.01.22 22:19:09 LOG7[81278:134651904]: RAND_status claims sufficient entropy for the PRNG 2008.01.22 22:19:09 LOG7[81278:134651904]: PRNG seeded successfully 2008.01.22 22:19:09 LOG7[81278:134651904]: Certificate: /usr/local/CA/stunnel.pem 2008.01.22 22:19:09 LOG7[81278:134651904]: Certificate loaded 2008.01.22 22:19:09 LOG7[81278:134651904]: Key file: /usr/local/CA/stunnel.pem 2008.01.22 22:19:09 LOG7[81278:134651904]: Private key loaded 2008.01.22 22:19:09 LOG7[81278:134651904]: SSL context initialized for service stunnel ^] telnet> q Connection closed. ...and some are written to the file I specified, dwiest(a)dfwdamian.vail: cat /tmp/stunnel.log 2008.01.22 22:19:09 LOG5[81278:134651904]: stunnel 4.21 on i386-unknown-freebsd6.2 with OpenSSL 0.9.7e-p1 25 Oct 2004 2008.01.22 22:19:09 LOG5[81278:134651904]: Threading:PTHREAD SSL:ENGINE Sockets:POLL,IPv6 Auth:LIBWRAP 2008.01.22 22:19:09 LOG7[81278:134651904]: stunnel started 2008.01.22 22:19:09 LOG7[81278:134651904]: FD 0 in non-blocking mode 2008.01.22 22:19:09 LOG7[81278:134651904]: FD 1 in non-blocking mode 2008.01.22 22:19:09 LOG7[81278:134651904]: stunnel permitted by libwrap from 127.0.0.1:53961 2008.01.22 22:19:09 LOG5[81278:134651904]: stunnel accepted connection from 127.0.0.1:53961 2008.01.22 22:19:09 LOG7[81278:134651904]: SSL state (accept): before/accept initialization 2008.01.22 22:19:11 LOG3[81278:134651904]: SSL_accept: Peer suddenly disconnected 2008.01.22 22:19:11 LOG5[81278:134651904]: Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket 2008.01.22 22:19:11 LOG7[81278:134651904]: stunnel finished (0 left) If I run stunnel in daemon mode with the debug level set to 7, then the messages are printed to stderr. Shouldn't they go to either syslog, or to the file specified with the "output" option? I dug through the source code and discovered that file_putline() is being called from parse_config() before open_log() has been called. This results in file_putline() writing to stderr instead of the specified output file. If this is known behavior, then it would be nice if the man page mentioned something. -Damian

3 3

rtmps with stunnel
by David Schulberg 24 Jan '08

24 Jan '08

Hi, A while ago I reported an issue with using rtmps on linux to connect to a Red5 server through stunnel. I am having no issues on Windows. The rtmps connection is made from Flash code running in the browser. The error reported on Linux was 'SSL_accept: Peer suddenly disconnected' which occurs straight after 'SSL state (accept): before/accept initialization' . Now I am having a similar problem trying to connect from a MAC. In this case I also get 'SSL_accept: Peer suddenly disconnected' which occurs straight after 2008.01.24 16:39:31 LOG7[1608:2980]: SSL state (accept): before/accept initialization 2008.01.24 16:39:31 LOG7[1608:2980]: SSL state (accept): SSLv3 read client hello A 2008.01.24 16:39:31 LOG7[1608:2980]: SSL state (accept): SSLv3 write server hello A 2008.01.24 16:39:31 LOG7[1608:2980]: SSL state (accept): SSLv3 write certificate A 2008.01.24 16:39:31 LOG7[1608:2980]: SSL state (accept): SSLv3 write server done A 2008.01.24 16:39:31 LOG7[1608:2980]: SSL state (accept): SSLv3 flush data It seems to get further on the MAC but still fails. Regards, David

1 0

stunnel with Fedora core
by Andy 17 Jan '08

17 Jan '08

Hello everyone I am trying to configure stunnel on a Fedora Core machine, but have had little luck. The below configuration is in the /etc/stunne/stunnel.conf. I want this machine to send encrypted data to another machine via stunnel. My knowledge of stunnel is quite limited. chroot = /home/stunnel pid = /stunnel.pid setuid = stunnel setgid = stunne; debug = 7 output = /var/log/messages client = yes [ldap] accept = 389 connect = ldap.example.com:636 I have been told that this command will work. stunnel -c -d ldaps -r <LDAPSERVER>:ldaps This command does work under debian but does not work under fedora core. Can anyone help me with this? -- REGARDS, Andy

1 0

Debian Bug#460019: cert= produces output on stderr even with log= set
by Luis Rodrigo Gallardo Cruz 16 Jan '08

16 Jan '08

----- Forwarded message from Bryan Donlan <bd(a)fushizen.net> ----- Version: 3:4.21-1 With the following configuration: output = /srv/stun/log compression = zlib CApath = /srv/stun/keys cert = /srv/stun/server.pem connect = localhost:9999 verify = 3 The following is output on stderr: 2008.01.10 02:54:19 LOG5[11786:3083495088]: Peer certificate location /srv/stun/keys This confuses clients when stunnel is driven direcly from xinetd. This output, if it is produced at all, should be placed in the log file. ----- End forwarded message ----- The issue is that verify_init (verify.c:103) calls s_log(LOG_NOTICE, "Peer certificate location %s", section->ca_dir); apparently before the logfile is setup. Could the log file initialization be moved earlier in the starup sequence? Or maybe this log call's severity could be lowered.

2 6

Nessus crashes stunnel
by Joe Kemp 16 Jan '08

16 Jan '08

I am running some tests against my stunnel configuration with Nessus. I am able to get stunnel to exit silently when I run Nessus with the Nessus TCP Scan and Weak Supported SSL Cipher Suites test. I have played with a few different options but the process consistently ends when these tests are run together. Here is the config: Linux testssl.capwin.net 2.6.18-53.1.4.el5 #1 SMP Fri Nov 30 00:45:16 EST 2007 i686 i686 i386 GNU/Linux gcc version 4.1.2 20070626 (Red Hat 4.1.2-14) stunnel 4.20 on i686-pc-linux-gnu with OpenSSL 0.9.8b 04 May 2006 Threading:PTHREAD SSL:ENGINE Sockets:POLL,IPv4 Auth:LIBWRAP OpenSSL 0.9.8b 04 May 2006 Tail of log file during nessus tests 2008.01.15 21:24:30 LOG5[10646:3086605200]: XMPP accepted connection from 10.102.11.250:41781 2008.01.15 21:24:30 LOG7[10646:3086605200]: SSL state (accept): before/accept initialization 2008.01.15 21:24:30 LOG7[10646:3086605200]: SSL alert (write): fatal: handshake failure 2008.01.15 21:24:30 LOG3[10646:3086605200]: SSL_accept: 1408A10B: error:1408A10B:SSL routines:SSL3_GET_CLIENT_HELLO:wrong version number 2008.01.15 21:24:30 LOG5[10646:3086605200]: Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket 2008.01.15 21:24:30 LOG7[10646:3086605200]: XMPP finished (0 left) 2008.01.15 21:24:30 LOG7[10646:3086608080]: XMPP accepted FD=7 from 10.102.11.250:41782 2008.01.15 21:24:30 LOG7[10646:3086605200]: XMPP started 2008.01.15 21:24:30 LOG7[10646:3086605200]: FD 7 in non-blocking mode 2008.01.15 21:24:30 LOG7[10646:3086605200]: TCP_NODELAY option set on local socket 2008.01.15 21:24:30 LOG7[10646:3086605200]: FD 8 in non-blocking mode 2008.01.15 21:24:30 LOG7[10646:3086605200]: FD 9 in non-blocking mode 2008.01.15 21:24:30 LOG7[10646:3086608080]: Cleaning up the signal pipe 2008.01.15 21:24:30 LOG6[10646:3086608080]: Child process 10676 finished with code 0 2008.01.15 21:24:30 LOG7[10646:3086605200]: Connection from 10.102.11.250:41782 permitted by libwrap 2008.01.15 21:24:30 LOG5[10646:3086605200]: XMPP accepted connection from 10.102.11.250:41782 2008.01.15 21:24:30 LOG7[10646:3086605200]: SSL state (accept): before/accept initialization Joe A. Kemp CapWIN Senior Systems Architect 6305 Ivy Lane Suite 300 Greenbelt, MD 20770 (P) 301-614-3727 (F) 301-614-0581

2 1

Re: [stunnel-users] stunnel automatically listening to extra ports: BAD
by Luis Rodrigo Gallardo Cruz 12 Jan '08

12 Jan '08

[You forgot to cc: the list] On Fri, Jan 11, 2008 at 03:24:32PM -0500, Alan Pinstein wrote: > On Jan 11, 2008, at 3:02 PM, Luis Rodrigo Gallardo Cruz wrote: >> On Fri, Jan 11, 2008 at 02:31:58PM -0500, Alan Pinstein wrote: >>> Hi All- >>> [ Stunnel listens on ports it shouldn't ] >>> >>> If I start up stunnel from the command line as "root" or another user >>> even, it only listens on the port listed in the conf file. >> >> Could you have some startup script that's automatically getting run >> with your logrotate scripts? >> > The problem happens the MOMENT stunnel starts. It has nothing to do with > the logrotate scripts. Oh, sorry, I got confused. (/me goes and re-reads the original mail ...) > I've done a bunch of debugging and can't figure out what's going on. > I have only one guess: stunnel automatically listens on any ports > that the process calling stunnel is listening on, in some sort of > attempt to seamlessly add SSL to existing daemons. I can't find any > docs or tell from the source code, but it's the only idea I can't > rule out... All this is in a *nix, right? The following is an educated guess: Open connections are open file descriptors, and fork()/exec() do not close open file descriptors. Thus, stunnel is inheriting the open connection. And, since it knows nothing about it, it does not close it or anything like that. So it's not that it activelly listens on it, but only that it does not bother to stop. You might check this theory by trying to connect to the port *after* apache is shut down. If I'm right you should get no answer at all. So, the solution is to have the file descriptors close when exec'ing stunnel. PHP or apache might have some option somewhere to do that (look for "close on exec" or something similarly named), but if not, you might have to write some sort of wrapper to do it. It's a messy thing, because AFAIK there's no clean way to do it short of for (i = 0; i < [some-hopefuly-large-enough-value]; i++) close(i); where the [large-enough-value] is determined by your system's file descriptor limit and your desire not to loop all the way to 2^32 or something. -- Rodrigo i-think-this-time-i-answered-the-question-asked Gallardo GPG-Fingerprint: 7C81 E60C 442E 8FBC D975 2F49 0199 8318 ADC9 BC28

5 4

Re: [stunnel-users] config socket SSL TCP
by khaled khaled 12 Jan '08

12 Jan '08

Hi,Can you send me please ( certificate+Key: Client & server) + CA.i want to try my server.The Client is a socket TCP developped on Openssl and C++.(I 'am sure that theclient work) but my config ???i want to generate a key for the client?the SSL client authenticate itself.Many thanks,FOR the server:-----BEGIN RSA PRIVATE KEY-----MIICXAIBAAKBgQDEIXwTWeacXiNOICmkgTgc+MD/i1w1sJ3LBR/lfnH+9pfs/6HBKY4SW+GHQtlSiHVx0WNQgoPQIU1J29PPWONYivIe2hdSvn1uSSmypa7gudWxUqBYuFKzzlmEMtFmUn8UG5KmV8SYQ/970C1bcEchWMyp40C+f9vkP3U/SmFBAwIDAQABAoGAQaWzkgaVWeFoj83UImveDFR2xRIwWwgyyLF+a6JXJbAESh+GVNFD7IE0i8GkXCuwo9giFeCZniCHbiFWVCC8d1/PZd/inQGfmtdTNbvr9xI7AVTTAH4D+mZTwduAuOAUdoI/r5+Ll/hyfZDdFMZuypbFHCUBspkNIfHymJ8qNwECQQD3Q16K1iuwRjZF7Pwl8YT3t8otnMawilFsV5f3RpGlxCT8yGH23liidPr9cwUCORRT4Lar98a9B77E7lTZEzQJAkEAyw+YW9pNqH13+nvcOkIVwefl1umNuU5ayye7gYi5xuccaoc2AnjtPPX8lSvM9ZNcT/0YQZSAsRfMm7YIq+dHqwJBAIZBDhRUNWSAuvc8tavkd04JfL1HYpp4f71T0i9xIaPf3DVkl8xy7a1H1v/Gc/HBDEh+urCk2EPK8Mn8nhU/WAECQAVikn3NGkYfnbDs2/hHjGAqEDRU2UdSxqGgmh5jS9n0gxJoJ4yFPHVjaKFkGflhQQ91/NCwaYFIykpO14gHiCUCQHkB8W/4zaB47skmB181p9WNiprWZRgqo4BINW6ecVQfc87s7+Jaz3GgRyCJ4QeUtbimOVd3wBO3FqzCyOnOLpY=-----END RSA PRIVATE KEY----------BEGIN CERTIFICATE-----MIICdzCCAeCgAwIBAgIBBzANBgkqhkiG9w0BAQQFADCBhDELMAkGA1UEBhMCRlIxDjAMBgNVBAgTBVBBUklTMQ4wDAYDVQQHEwVQQVJJUzEhMB8GA1UEChMYSW50ZXJuZXQgV2lkZ2l0cyBQdHkgTHRkMQ8wDQYDVQQDEwZraGFsZWQxITAfBgkqhkiG9w0BCQEWEmtraGFsZWRAaG90bWFpbC5mcjAeFw0wODAxMDgxOTQ5NDJaFw0xODAxMDUxOTQ5NDJaMDAxDzANBgNVBAMTBmNsaWVudDEdMBsGCSqGSIb3DQEJARYObmR0QHdhdmVjb20uZnIwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAMQhfBNZ5pxeI04gKaSBOBz4wP+LXDWwncsFH+V+cf72l+z/ocEpjhJb4YdC2VKIdXHRY1CCg9AhTUnb089Y41iK8h7aF1K+fW5JKbKlruC51bFSoFi4UrPOWYQy0WZSfxQbkqZXxJhD/3vQLVtwRyFYzKnjQL5/2+Q/dT9KYUEDAgMBAAGjTDBKMBkGA1UdEQQSMBCBDm5kdEB3YXZlY29tLmZyMAwGA1UdEwEB/wQCMAAwHwYDVR0jBBgwFoAU2LdfcyCatRPpCalV3Qyq7RJwUjowDQYJKoZIhvcNAQEEBQADgYEAMcC80wuYfwycQF/6mbG2D4iQJkUJGXyWd2ColwPvxos5S07oUyPpy1ev+OVmHCSMZMuBpGsJ+0oNyqe39wWvvjB80pddXaKcRN4lNj7BSo2u/edy8WRoFjj75JV3Z35K5KmMAGs2MS7Np/sHa4CVlu5yd8gI0CIA5gxXwqPNJV8=-----END CERTIFICATE-----For CA ROOT:-----BEGIN RSA PRIVATE KEY-----MIICXwIBAAKBgQDCK1KTB2TkLVbNYnU9t29ZmlClEnszHa/xX8slB/VnFdazw/U2iSS01OtwXaUNTrA/hQJ50ykls14dRBguwJnNuGM8IH8zCCWNdesTMtYF0ZucCkrfSmir9210A2m6Wo1SEbKyUHErFMsW9UcxDPAGyfZQ0dIhjUDDkw9SL+fTPQIDAQABAoGBAJm3SGDjqqjFiAGC38QjM0DhXNTCA8ycxQw2xREk8s9QR6/7A2bQPcH3Cgjj6eXWFMvElggx9lJFZM2QegCRM3B7DlB4VYviCz+T5urezuRiHZkxfHp6m2T9fitcfB+FUCq3uGn3yeA+rLc/P5/dXV3JE1uNmH96p96e6kwRnorBAkEA6eDPz7dIh+2znbCcoyrX4G5tp7DqNooBH5p5gLp9an7DePgfHH15POZfCQ4oNv16VIfPhM8fF9u8tmbs5jjFsQJBANSI/OdNitlQYXCoUuDqgPbsxhnS6ajVUa7ZlMoGgkLCmuSj99gphD0q6tp/9niEhAdp36wSyerEZKvu5TEobU0CQQDZGEeOhpGbK3iJLcGYbFKLD7ZV7JDcI2o7jcavSWzVh+mmxpsKdSYu86DP5QZLVStSf+aPXzt7iAs6PXw1kAlhAkEAwywVSverdUraYFFC4qaWzaq7dMV5q4BRpYbLmwaFIneBNEva8teVR3Kc/xAZr6zJbeFs9KDAaeX2KOmV8SGV1QJBAKGPzYwD5XpW3v9NpmyNYzFf4HuzK6Gh90aZ5CLxSSdDHc9cmCZEgoXgepb6/48+qRpRELkSpeE2IWHBxmGMPa8=-----END RSA PRIVATE KEY----------BEGIN CERTIFICATE-----MIIDZTCCAs6gAwIBAgIBADANBgkqhkiG9w0BAQQFADCBhDELMAkGA1UEBhMCRlIxDjAMBgNVBAgTBVBBUklTMQ4wDAYDVQQHEwVQQVJJUzEhMB8GA1UEChMYSW50ZXJuZXQgV2lkZ2l0cyBQdHkgTHRkMQ8wDQYDVQQDEwZraGFsZWQxITAfBgkqhkiG9w0BCQEWEmtraGFsZWRAaG90bWFpbC5mcjAeFw0wODAxMDgxOTIyMTlaFw0xODAxMDUxOTIyMTlaMIGEMQswCQYDVQQGEwJGUjEOMAwGA1UECBMFUEFSSVMxDjAMBgNVBAcTBVBBUklTMSEwHwYDVQQKExhJbnRlcm5ldCBXaWRnaXRzIFB0eSBMdGQxDzANBgNVBAMTBmtoYWxlZDEhMB8GCSqGSIb3DQEJARYSa2toYWxlZEBob3RtYWlsLmZyMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDCK1KTB2TkLVbNYnU9t29ZmlClEnszHa/xX8slB/VnFdazw/U2iSS01OtwXaUNTrA/hQJ50ykls14dRBguwJnNuGM8IH8zCCWNdesTMtYF0ZucCkrfSmir9210A2m6Wo1SEbKyUHErFMsW9UcxDPAGyfZQ0dIhjUDDkw9SL+fTPQIDAQABo4HkMIHhMB0GA1UdDgQWBBTYt19zIJq1E+kJqVXdDKrtEnBSOjCBsQYDVR0jBIGpMIGmgBTYt19zIJq1E+kJqVXdDKrtEnBSOqGBiqSBhzCBhDELMAkGA1UEBhMCRlIxDjAMBgNVBAgTBVBBUklTMQ4wDAYDVQQHEwVQQVJJUzEhMB8GA1UEChMYSW50ZXJuZXQgV2lkZ2l0cyBQdHkgTHRkMQ8wDQYDVQQDEwZraGFsZWQxITAfBgkqhkiG9w0BCQEWEmtraGFsZWRAaG90bWFpbC5mcoIBADAMBgNVHRMEBTADAQH/MA0GCSqGSIb3DQEBBAUAA4GBAENN2yi1jGD87BjzQ7PfmmRiwP7psisy8GKv4ipRhho76Su353BOZJXNj1x+gyk1/gsDVeSRf0YDJTiH6bMLY2usC9UA3F7x6zvb36joVxbnKLNhxrXStYIaJgVYW+Pf8Wr3sXO/yAkiyDsCsDseofnSGrirPsMC0N9n5X5qf+ER-----END CERTIFICATE-----FOR the Client-----BEGIN CERTIFICATE-----MIICdzCCAeCgAwIBAgIBBjANBgkqhkiG9w0BAQQFADCBhDELMAkGA1UEBhMCRlIxDjAMBgNVBAgTBVBBUklTMQ4wDAYDVQQHEwVQQVJJUzEhMB8GA1UEChMYSW50ZXJuZXQgV2lkZ2l0cyBQdHkgTHRkMQ8wDQYDVQQDEwZraGFsZWQxITAfBgkqhkiG9w0BCQEWEmtraGFsZWRAaG90bWFpbC5mcjAeFw0wODAxMDgxOTQ2MzhaFw0xODAxMDUxOTQ2MzhaMDAxDzANBgNVBAMTBnNlcnZlcjEdMBsGCSqGSIb3DQEJARYOa2toQHdhdmVjb20uZnIwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAM9Sl2bn98NylY7KITLL//vJsr0OeuS79qTBdy2ticIWjz4k9/iVDQ7YmvxlxR5KtY1kSZYaSU44lXATH15ukczGWo2qy9uNfA5PhsEIUsE3SaQA+EptaicHQhsZ3QkLypz4gqNqK8Im/Nk4qvTR9Z7pturgROFOsckwOdSYbkC3AgMBAAGjTDBKMBkGA1UdEQQSMBCBDmtraEB3YXZlY29tLmZyMAwGA1UdEwEB/wQCMAAwHwYDVR0jBBgwFoAU2LdfcyCatRPpCalV3Qyq7RJwUjowDQYJKoZIhvcNAQEEBQADgYEAAfP0JXQlbi0GUIE04dYsCqug2D/l8+PtRuZ0iRUSznwhc5H7nkTeAV/i91BIBC3NtKdlhj6COcCApEVD9Jbax2dPJBm9ZCccVC41qKaD5Wi82y0aK7yIF+EvPGAieSWphhRbNH4ElF/rWADaIGMJz2PqtE0WgptDOfH5z/mn2MM=-----END CERTIFICATE----------BEGIN RSA PRIVATE KEY-----MIICXwIBAAKBgQDPUpdm5/fDcpWOyiEyy//7ybK9Dnrku/akwXctrYnCFo8+JPf4lQ0O2Jr8ZcUeSrWNZEmWGklOOJVwEx9ebpHMxlqNqsvbjXwOT4bBCFLBN0mkAPhKbWonB0IbGd0JC8qc+IKjaivCJvzZOKr00fWe6bbq4EThTrHJMDnUmG5AtwIDAQABAoGBAL00oNvXY3RJhFgV/ApBxtJhFvAW4O0S5Vsi/MMBFzG8KOoMDwob7RjZcUhbEHQ+tkXdepK0VqY+WZM4wG4L9p4IzpvU1CgLcPXf9zw7JLFZITMux1WhDCT/HEnr/sh138va7b7HXOl7TSgBrmo8xyPNktzqsye2TXiRU6rSHjjhAkEA7W+VnzA5V1T/H5N2p3V4Hy6P9Kv83nTqlq4JP9S939/1JYF2ZrdFPluNOO1Gn3PDFhuKZekFvvBdjXq8EH3H/wJBAN+IRdqFvah0smfASV3bEPbP1tl7JwsaOb8UqQciZHkwzQztHrZ7Gf3s+5HvMcQj4TMR9Dl4ad00kmB6pVnnx0kCQQCCBuOXY99jFicI8ca++jOoT+WCBlXatYhqsDBchnLdEVa9DWL76U3AUn7KOBa+57RkfPyTxsLgx91Tx20KUvedAkEAxd2+17xjMeZ6tdREHUx5K8C2kjStTuqcC0Siiqoq/gvwtmx/L1CwpVFNLtTo3JJWGfrekLDCJQkQOU7XZ0n/4QJBAOMpeKnf+ZXAuyhY9DVeCWK9G3MP/2VZuC7Z5N56P5VVk22mxe9LdyMdA2FG69fIuoaT9Uni/yD+tzRb6PJTDzM=-----END RSA PRIVATE KEY----- _________________________________________________________________ Comme 9 millions de français, créez un compte Hotmail ! http://www.windowslive.fr/hotmail/default.asp

1 0

stunnel automatically listening to extra ports: BAD
by Alan Pinstein 11 Jan '08

11 Jan '08

Hi All- I am using stunnel to secure a connection between a local python script using telnetlib and a custom sockets-based server requiring SSL, from local port 4449 to remote port 4449. This is done via: stunnel /opt/www/domains/admin.showcasere.com/showcase/classes/ opensrs-php/stunnel-app.conf where the conf file is: > client = yes > pid = /opt/www/domains/admin.showcasere.com/runtime/stunnel.pid > debug = 7 > [telnet] > accept = 4449 > connect = admin.hostedemail.com:4449 Functionally, everything works for my application, but I am experiencing a bad side-effect. stunnel is ALSO setting up listeners on HTTP and HTTPS ports, and when my daily logrotate scripts run and HUP apache, stunnel steals the web server's ports and the server won't come back up! I had 7 hours of downtime today because of this. I've done a bunch of debugging and can't figure out what's going on. I have only one guess: stunnel automatically listens on any ports that the process calling stunnel is listening on, in some sort of attempt to seamlessly add SSL to existing daemons. I can't find any docs or tell from the source code, but it's the only idea I can't rule out... Here is the debug log of the startup of stunnel (which is run from an apache/php script): Jan 11 13:10:13 bigwoody stunnel: LOG5[13964:3086333632]: stunnel 4.14 on i386-redhat-linux-gnu PTHREAD+POLL+IPv6+LIBWRAP with OpenSSL 0.9.8a 11 Oct 2005 Jan 11 13:10:13 bigwoody stunnel: LOG7[13964:3086333632]: RAND_status claims sufficient entropy for the PRNG Jan 11 13:10:13 bigwoody stunnel: LOG6[13964:3086333632]: PRNG seeded successfully Jan 11 13:10:13 bigwoody stunnel: LOG6[13964:3086333632]: file ulimit = 1024 (can be changed with 'ulimit -n') Jan 11 13:10:13 bigwoody stunnel: LOG6[13964:3086333632]: poll() used - no FD_SETSIZE limit for file descriptors Jan 11 13:10:13 bigwoody stunnel: LOG5[13964:3086333632]: 500 clients allowed Jan 11 13:10:13 bigwoody stunnel: LOG7[13964:3086333632]: FD 31 in non-blocking mode Jan 11 13:10:13 bigwoody stunnel: LOG7[13964:3086333632]: FD 32 in non-blocking mode Jan 11 13:10:13 bigwoody stunnel: LOG7[13964:3086333632]: FD 33 in non-blocking mode Jan 11 13:10:13 bigwoody stunnel: LOG7[13964:3086333632]: SO_REUSEADDR option set on accept socket Jan 11 13:10:13 bigwoody stunnel: LOG7[13964:3086333632]: telnet bound to 0.0.0.0:4449 Jan 11 13:10:13 bigwoody stunnel: LOG7[13965:3086333632]: Created pid file /opt/www/domains/admin.showcasere.com/runtime/stunnel.pid Jan 11 13:10:13 bigwoody stunnel: LOG7[13965:3086333632]: telnet accepted FD=34 from 127.0.0.1:48335 Jan 11 13:10:13 bigwoody stunnel: LOG7[13965:3086330784]: telnet started Jan 11 13:10:13 bigwoody stunnel: LOG7[13965:3086330784]: FD 34 in non-blocking mode Jan 11 13:10:13 bigwoody stunnel: LOG7[13965:3086330784]: FD 35 in non-blocking mode Jan 11 13:10:13 bigwoody stunnel: LOG7[13965:3086330784]: FD 36 in non-blocking mode Jan 11 13:10:13 bigwoody stunnel: LOG7[13965:3086333632]: Cleaning up the signal pipe Jan 11 13:10:13 bigwoody stunnel: LOG6[13965:3086333632]: Child process 13967 finished with code 0 Jan 11 13:10:13 bigwoody stunnel: LOG7[13965:3086330784]: Connection from 127.0.0.1:48335 permitted by libwrap Jan 11 13:10:13 bigwoody stunnel: LOG5[13965:3086330784]: telnet connected from 127.0.0.1:48335 Jan 11 13:10:13 bigwoody stunnel: LOG7[13965:3086330784]: FD 35 in non-blocking mode Jan 11 13:10:13 bigwoody stunnel: LOG7[13965:3086330784]: telnet connecting 216.40.42.6:4449 Jan 11 13:10:13 bigwoody stunnel: LOG7[13965:3086330784]: connect_wait: waiting 10 seconds Jan 11 13:10:13 bigwoody stunnel: LOG7[13965:3086330784]: connect_wait: connected Jan 11 13:10:13 bigwoody stunnel: LOG7[13965:3086330784]: Remote FD=35 initialized Jan 11 13:10:13 bigwoody stunnel: LOG7[13965:3086330784]: SSL state (connect): before/connect initialization Jan 11 13:10:13 bigwoody stunnel: LOG7[13965:3086330784]: SSL state (connect): SSLv3 write client hello A Jan 11 13:10:13 bigwoody stunnel: LOG7[13965:3086330784]: SSL state (connect): SSLv3 read server hello A Jan 11 13:10:13 bigwoody stunnel: LOG7[13965:3086330784]: SSL state (connect): SSLv3 read server certificate A Jan 11 13:10:13 bigwoody stunnel: LOG7[13965:3086330784]: SSL state (connect): SSLv3 read server done A Jan 11 13:10:13 bigwoody stunnel: LOG7[13965:3086330784]: SSL state (connect): SSLv3 write client key exchange A Jan 11 13:10:13 bigwoody stunnel: LOG7[13965:3086330784]: SSL state (connect): SSLv3 write change cipher spec A Jan 11 13:10:13 bigwoody stunnel: LOG7[13965:3086330784]: SSL state (connect): SSLv3 write finished A Jan 11 13:10:13 bigwoody stunnel: LOG7[13965:3086330784]: SSL state (connect): SSLv3 flush data Jan 11 13:10:13 bigwoody stunnel: LOG7[13965:3086330784]: SSL state (connect): SSLv3 read finished A Jan 11 13:10:13 bigwoody stunnel: LOG7[13965:3086330784]: 1 items in the session cache Jan 11 13:10:13 bigwoody stunnel: LOG7[13965:3086330784]: 1 client connects (SSL_connect()) Jan 11 13:10:13 bigwoody stunnel: LOG7[13965:3086330784]: 1 client connects that finished Jan 11 13:10:13 bigwoody stunnel: LOG7[13965:3086330784]: 0 client renegotiatations requested Jan 11 13:10:13 bigwoody stunnel: LOG7[13965:3086330784]: 0 server connects (SSL_accept()) Jan 11 13:10:13 bigwoody stunnel: LOG7[13965:3086330784]: 0 server connects that finished Jan 11 13:10:13 bigwoody stunnel: LOG7[13965:3086330784]: 0 server renegotiatiations requested Jan 11 13:10:13 bigwoody stunnel: LOG7[13965:3086330784]: 0 session cache hits Jan 11 13:10:13 bigwoody stunnel: LOG7[13965:3086330784]: 0 session cache misses Jan 11 13:10:13 bigwoody stunnel: LOG7[13965:3086330784]: 0 session cache timeouts Jan 11 13:10:13 bigwoody stunnel: LOG6[13965:3086330784]: SSL connected: new session negotiated Jan 11 13:10:13 bigwoody stunnel: LOG6[13965:3086330784]: Negotiated ciphers: RC4-MD5 SSLv3 Kx=RSA Au=RSA Enc=RC4 (128) Mac=MD5 Jan 11 13:10:13 bigwoody stunnel: LOG7[13965:3086330784]: SSL socket closed on SSL_read Jan 11 13:10:13 bigwoody stunnel: LOG7[13965:3086330784]: Socket write shutdown Jan 11 13:10:13 bigwoody stunnel: LOG5[13965:3086330784]: Connection closed: 91 bytes sent to SSL, 73 bytes sent to socket Jan 11 13:10:13 bigwoody stunnel: LOG7[13965:3086330784]: telnet finished (0 left) And then, you can see what stunnel is listening on: [root@bigwoody custom_img]# lsof -i | grep stunnel stunnel 13965 apache 4u IPv4 156503478 TCP static-216.114.79.43.primarynetwork.com:http (LISTEN) stunnel 13965 apache 5u IPv4 156503480 TCP static-216.114.79.43.primarynetwork.com:https (LISTEN) stunnel 13965 apache 30u IPv4 156771437 TCP localhost.localdomain:51333->localhost.localdomain:9676 (ESTABLISHED) stunnel 13965 apache 33u IPv4 156846546 TCP *:privatewire (LISTEN) If I start up stunnel from the command line as "root" or another user even, it only listens on the port listed in the conf file. Does anyone have any idea what's going on here? How can I turn off this behavior? Thanks! Alan

2 1

Re: [stunnel-users] your mail
by Brian Hatch 10 Jan '08

10 Jan '08

On or about 2008-01-10 15:34 +0100, khaled45(a)free.fr directed: > Here attached files generated. > can you send me the configuration element of SSL and Stunnel or explain me how > to generate? You sent the private keys too - you shouldn't do this. You should create new keys when done debugging this problem. I saw only 2 keys - the CA and the stunnel.pem. Your configuration specifies 3 keys, the CA, stunnel.pem, and is attempting to verify the SSL client (browser? something else) against the CA via the 'verify=' line. What is the SSL client? Did you generate a key for it? Because your config is requiring the SSL client authenticate itself, and Stunnel is dropping the connection because that phase isn't working correctly. -- Brian Hatch "So, what's the problem?" Systems and "I don't know. Security Engineer *That's* the problem." http://www.ifokr.org/bri/ Every message PGP signed

1 0

Re: [stunnel-users] your mail
by Brian Hatch 09 Jan '08

09 Jan '08

At more or less 2008-01-09 18:09 +0100, khaled45(a)free.fr squalked: > ; It's often easier to use CAfile > CAfile = ca.pem > cert = userkey.pem > debug = 7 > client = no > [apache] > accept = 4433 > connect = 192.168.1.4:433 I'd suggest using the full path for your pem files above, just to be safe. Can you shoot the public keys of the client (which is not on this machine) and the ca.pem and the public key from userkey.pem (which is actually the server's key - you may wish to rename.) There are three pems involved: * the CA key (private) and cert (public) in ca.pem * the stunnel server's key (private) and cert (public) in userkey.pem. ('userkey' is a bad name here.) * the client's key (private) and cert (public) on 192.168.1.5. Can you send the public parts here so I can verify that they're signed by the appropritate folks? -- Brian Hatch "Everybody's cute! Systems and Everybody's cute! Security Engineer Even me. But in http://www.ifokr.org/bri/ purple I'm stunning!" Every message PGP signed

1 0

TCP (Server / Client)
by khaled khaled 09 Jan '08

09 Jan '08

Hi all, I am a new STUNNEL user,I will do 2 secure sockets TCP (Server / Client). I would like to know how to set 'stunnel.conf. I tried but it does not work. Description: ---------- I created a CA root and from this I have created 2 pairs (key and certificate) one for the server and one for the client. You can send me please a config file of the server. Many thanks, Stunnel.config (serveur) ----------------------- cert = server.crt key = serverkey.key CAfile = ca.crt ;[Server] accept = 192.168.1.4:4433 connect = 192.168.1.4:4433 _________________________________________________________________ Votre contact a choisi Hotmail, l'e-mail nouvelle génération. Créez un compte. http://www.windowslive.fr/hotmail/default.asp

3 6

2 secure sockets TCP (Server / Client).
by khaled khaled 07 Jan '08

07 Jan '08

Hi all,I am a new STUNNEL user,I will do 2 secure sockets TCP (Server / Client). I would like to know how to set 'stunnel.conf. I tried but it does not work. Description: ---------- I created a CA root and from this I have created 2 pairs (key and certificate) one for the server and one for the client. You can send me please a config file from a server? Many thanks, Stunnel.config (serveur) ----------------------- ; Sample stunnel configuration file by Michal Trojnara 2002-2006; 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.pemcert = server.crt key = serverkey.key ; Some performance tuningssocket = l:TCP_NODELAY=1socket = r:TCP_NODELAY=1 CAfile = ca.crt ;[Server]accept = 192.168.1.4:4433connect = 192.168.1.4:4433 KHALED Khaled Ingénieur de télécommunications et informatique _________________________________________________________________ Votre contact a choisi Hotmail, l'e-mail nouvelle génération. Créez un compte. http://www.windowslive.fr/hotmail/default.asp

1 0

Missing Something Basic on Config
by Steve 29 Dec '07

29 Dec '07

Using stunnel for NNTPS. Stunnel starts without any apparent problems (log looks normal), but simply doesn't intercept packets from my news reader. There is no activity in the log and sniffing the packets shows everything happening on 119. My understanding of the concept is that there are no configuration changes needed in the newsreader; IOW, I leave it pointing to the unsecured NNTP server with the port set to 119. I fear I'm missing something very obvious. BTW, I've confirmed the ability to use NNTPS with this particular server by using Outlook Express, which is compatible with NNTPS. Version: 4.20; I used the Windows binary. Running XP. Config: ; Some performance tunings socket = l:TCP_NODELAY=1 socket = r:TCP_NODELAY=1 ; Some debugging stuff useful for troubleshooting debug = 7 output = stunnel.log ; Use it for client mode client = yes ; Service-level configuration [nntps] accept = 192.168.1.101:119 connect = secure.news.easynews.com:563 Log: 2007.12.28 22:24:46 LOG5[6640:6644]: stunnel 4.20 on x86-pc-mingw32-gnu with OpenSSL 0.9.8d 28 Sep 2006 2007.12.28 22:24:46 LOG5[6640:6644]: Threading:WIN32 SSL:ENGINE Sockets:SELECT,IPv6 2007.12.28 22:24:46 LOG5[6640:5936]: No limit detected for the number of clients 2007.12.28 22:24:46 LOG7[6640:5936]: FD 196 in non-blocking mode 2007.12.28 22:24:46 LOG7[6640:5936]: SO_REUSEADDR option set on accept socket 2007.12.28 22:24:46 LOG7[6640:5936]: nntps bound to 192.168.1.101:119

1 0

Avoiding outlook express warning...
by fg 28 Dec '07

28 Dec '07

Hello all I use stunnel on a server with a stunnel.pem file generated with openSSL,( this file is not certified with verisign or others...) Each time i launch outlook express on a client a have a warning saying that the server is using a certificate who can't be verified.... I have to close this warning and after all is ok... Question Is it possible to skip this warning? perhaps with a public key approuved in outlook express??? thanks for help --------------------------------- Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail

3 2

stunnel
by peter griep 28 Dec '07

28 Dec '07

hello i'm using stunnel with download2day,but it's not working wih grabit can you tell what i must do to work stunnel with grabit. peter

3 2

1 tunnel client to few different servers
by Shalvi Ziv 26 Dec '07

26 Dec '07

All, As my PROXY server gets requests from end-users to be proxied to several different content providers (SMS servers), I was wondering how can encrypt the traffic between the PROXY to the SMS using stunnel, but still handle the differentiation to the various content providers. Meaning, my PROXY listens on port 9090 for all incoming SMS requests and each request should be addressed to different SMS server (i.e. different content provider) based on the number the message was sent to. See following example: Client = yes [SMPP] accept = 9090 (should always be this port) connect = <SMS IP>:442 Now, how can I do it with stunnel configuration (having the <SMS IP> flexibly assigned according to other parameters in the packet)? Thanks! zivs

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

stunnel-users