- stunnel-users - stunnel.org

Multiple Instances of stunnel
by dps_maillists＠mac.com 11 Feb '05

11 Feb '05

Hi everyone; Is it possible to run multiple instances of stunnel (v 4.07) in client mode on a single machine? We sould like to use stunnel to secure connections from a small number of client applications (1 to 10) connecting to a larger number of server applications (200 per client app). Ideally, we would like to use one instance of stunnel per client. Many thanks in advance. Doug

2 1

connect_wait: s_poll_wait timeout
by Alexander Lazic 07 Feb '05

07 Feb '05

Hi, we run stunnel on an solaris 9 with unlimited FD. Today we get the follwing error: connect_wait: s_poll_wait timeout With 'top' we see ~190-~220 threads and the client can't connect to our site. our config is: --- cert = /usr/local/apache/our.pem setuid = stunnel setgid = apache options = ALL pid = /usr/local/apache/logs/stunnel_netbanking.pid ciphers = ALL:!EXP1024-DHE-DSS-RC4-SHA:!EXP1024-RC4-SHA:!EXP1024-DHE-DSS-DES-CBC-SHA:!EXP1024-DES-CBC-SHA:!EXP1024-RC2-CBC-MD5:!EXP1024-RC4-MD5:!ADH:!EXP56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL:@STRENGTH debug = 6 output = /usr/local/apache/logs/stunnel_netbanking.log [https] accept = 10.3.169.208:443 connect = 10.3.169.208:10800 TIMEOUTclose = 0 xforwardedfor = yes --- stunnel 4.07 on sparc-sun-solaris2.9 PTHREAD+POLL+IPv4 with OpenSSL 0.9.7d 17 Mar 2004 PRNG seeded successfully file ulimit = 2147483647 (can be changed with 'ulimit -n') poll() used - no FD_SETSIZE limit for file descriptors 8388607 clients allowed --- Please can you help us to solve the problem. thx al ;-)

2 1

Problem downloading large files with sslv2
by Bhavesh Patel 04 Feb '05

04 Feb '05

Hi, I'm trying to download files from Internet Explorer using sslv2 and I keep getting the following message: 2005.02.04 16:45:04 LOG7[8237077:0]: FD 1 in non-blocking mode 2005.02.04 16:45:04 LOG7[8237077:0]: stunnel connecting 127.0.0.1:80 2005.02.04 16:45:04 LOG7[8237077:0]: remote connect #1: EINPROGRESS: retrying 2005.02.04 16:45:04 LOG7[8237077:0]: waitforsocket: FD=1, DIR=write 2005.02.04 16:45:04 LOG7[8237077:0]: waitforsocket: ok 2005.02.04 16:45:04 LOG7[8237077:0]: Remote FD=1 initialized 2005.02.04 16:45:04 LOG7[8237077:0]: SSL_read returned WANT_: retrying 2005.02.04 16:45:04 LOG7[8237077:0]: SSL closed on SSL_write 2005.02.04 16:45:04 LOG5[8237077:0]: Connection closed: 0 bytes sent to SSL, 669 bytes 2005.02.04 16:45:04 LOG7[8237077:0]: removing pid file /usr/local/var/run/stunnel.pid 2005.02.04 16:45:04 LOG7[2375710:0]: Process 8237077 finished with code 0 (0 left) Also does anyone know if that 10 TIMEOUTconnect for IE really works? Thanks, Bhavesh

1 0

concurrency request
by kevin 01 Feb '05

01 Feb '05

hi, I've recently set up stunnel for SSL connect. When I test its performance with siege with 700 concurrency request, I got this log: "Error: socket: connection timed out.: Operation now in progress" So, may I ask what is the upper limit of concurrency in stunnel, if the performance of the machine is good enough. and how can I increase the concurrency upper limit. thanks

2 1

Q: rereading configuration file?
by Heiko Nardmann 01 Feb '05

01 Feb '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! Does stunnel offer a way to signal a need for rereading the configuration file, i.e. some kind of SIGHUP ? I would like to add services while running stunnel without stopping the program ... it should compare currently available services with the new list of services, stop the ones not available any more and start those which are new in the new/changed configuration ... - -- Heiko Nardmann (Dipl.-Ing. Technische Informatik) secunet Security Networks AG - Sicherheit in Netzwerken (www.secunet.de), Weidenauer Str. 223-225, D-57076 Siegen Tel. : +49 271 48950-13, Fax : +49 271 48950-50 Besuchen Sie uns vom 10. - 16. März auf der CeBIT 2005 in Halle 7, Stand D38. Informationen zu unseren CeBIT-Themen finden Sie unter www.secunet.com <outbind://44/www.secunet.com> - wir freuen uns auf das Gespräch mit Ihnen. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFB/4Dzpm53PRScYygRAtg4AJ9Ku/8xfufFdrLq7cz2+1GDjrcvyQCffVLw v/2D0Fd8UtTHpssq7cgc71Y= =uG2t -----END PGP SIGNATURE-----

3 2

Q: error message during startup?
by Heiko Nardmann 01 Feb '05

01 Feb '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! I just got the following stunnel error message in my syslog: File descriptor out of range (1024>=1024) The reason is that I have tried to let stunnel create 2000 services. But where do I change the maximum for this range? (Linux) Kernel? Or stunnel? Thanks in advance! PS: I already changed ulimit to 4000. - -- Heiko Nardmann (Dipl.-Ing. Technische Informatik) secunet Security Networks AG - Sicherheit in Netzwerken (www.secunet.de), Weidenauer Str. 223-225, D-57076 Siegen Tel. : +49 271 48950-13, Fax : +49 271 48950-50 Besuchen Sie uns vom 10. - 16. März auf der CeBIT 2005 in Halle 7, Stand D38. Informationen zu unseren CeBIT-Themen finden Sie unter www.secunet.com <outbind://44/www.secunet.com> - wir freuen uns auf das Gespräch mit Ihnen. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFB/4TWpm53PRScYygRAv2JAKCHTe6zNvhmWAkypK5xymm+LWstEACgt1vJ vSNr7eeFXUpRFCu2SiY/4ls= =huyB -----END PGP SIGNATURE-----

2 1

Q: need of restart after CRL/CA directory contents change?
by Heiko Nardmann 31 Jan '05

31 Jan '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! Since I want to write CRL files from all relevant CAs based on a regular (daily) basis I wonder whether it is necessary to restart stunnel if the contents of the CRL or CA directory changes. The regular part is going to be handled by a cronjob which does an LDAP search which results in the CA certificate and crl files. How does stunnel work in this situation? Do I need a restart after a cron run or not? Thanks in advance! - -- Heiko Nardmann (Dipl.-Ing. Technische Informatik) secunet Security Networks AG - Sicherheit in Netzwerken (www.secunet.de), Weidenauer Str. 223-225, D-57076 Siegen Tel. : +49 271 48950-13, Fax : +49 271 48950-50 Besuchen Sie uns vom 10. - 16. März auf der CeBIT 2005 in Halle 7, Stand D38. Informationen zu unseren CeBIT-Themen finden Sie unter www.secunet.com <outbind://44/www.secunet.com> - wir freuen uns auf das Gespräch mit Ihnen. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFB/j+kpm53PRScYygRArxfAJ4mXXvjL+qEh6lBJlhpJJfC/jSoEQCgx4ie Xjv5/K3xcL6qPxp5ZH3SzOk= =4/pC -----END PGP SIGNATURE-----

2 1

Re: [stunnel-users] Stunnel 4.05/4.07 Crash
by PinLee_Su＠azuretech.com.sg 31 Jan '05

31 Jan '05

Hi Michal, The initial lines look like this:- 2005.01.25 15:21:23 LOG5[1160:2612]: stunnel 4.07 on x86-pc-mingw32-gnu WIN32+IPv4 with OpenSSL 0.9.7e 25 Oct 2004 2005.01.25 15:21:24 LOG5[1160:1828]: No limit detected for the number of clients 2005.01.25 15:21:24 LOG5[1160:1476]: HTTP connected from 10.3.5.137:2013 2005.01.25 15:21:25 LOG3[1160:1476]: readsocket: Connection reset by peer (WSAECONNRESET) (10054) 2005.01.25 15:21:25 LOG5[1160:1476]: Connection reset: 206 bytes sent to SSL, 250 bytes sent to socket 2005.01.25 15:21:25 LOG5[1160:2380]: HTTP connected from 10.3.5.137:2024 2005.01.25 15:21:25 LOG3[1160:2380]: readsocket: Connection reset by peer (WSAECONNRESET) (10054) 2005.01.25 15:21:25 LOG5[1160:2380]: Connection reset: 206 bytes sent to SSL, 226 bytes sent to socket 2005.01.25 15:21:25 LOG5[1160:1992]: HTTP connected from 10.3.5.137:2056 2005.01.25 15:21:27 LOG5[1160:2220]: HTTP connected from 10.3.5.137:2084 2005.01.25 15:21:31 LOG5[1160:2220]: Connection closed: 4969 bytes sent to SSL, 41208 bytes sent to socket 2005.01.25 15:21:31 LOG5[1160:1028]: HTTP connected from 10.3.5.137:2104 2005.01.25 15:21:40 LOG5[1160:1028]: Connection closed: 2528 bytes sent to SSL, 31275 bytes sent to socket 2005.01.25 15:21:40 LOG5[1160:512]: HTTP connected from 10.3.5.137:2122 2005.01.25 15:21:43 LOG5[1160:1992]: Connection closed: 12539 bytes sent to SSL, 56951 bytes sent to socket 2005.01.25 15:21:45 LOG5[1160:512]: Connection closed: 1689 bytes sent to SSL, 21416 bytes sent to socket 2005.01.25 15:21:46 LOG5[1160:2044]: HTTP connected from 10.3.5.137:2154 2005.01.25 15:21:47 LOG5[1160:2148]: HTTP connected from 10.3.5.137:2160 I have 11 config files as each one has its own client certificate. each one contains the follow:- CAfile=c:\STunnel\config\root.pem cert=c:\STunnel\config\myCert_A.pem client=Yes debug=7 output=c:\STunnel\logs\myCert_A.log [HTTP] accept=3885 connect=10.70.1.81:443 thanks and rgds,spl "Azure Technologies is the IT solutions provider of Hutchison Whampoa Limited and a member of Hutchison Global Communications Holdings Limited." The message is for information purposes only and is not intended to create legally binding relations. The shareholders, directors and management of Azure Technologies and any of its group companies accept no responsibility and accordingly shall have no liability to any party whatsoever with respect to the contents of this message. This message (including any attachments) is intended only for the use of the addressee(s) named above. It may contain information that is PRIVILEGED and CONFIDENTIAL and should not be read, copied or otherwise used by any other person. If you are not the intended recipient, please erase all copies of the message (including attachments) and notify us immediately. PinLee_Su@azuretech .com.sg To: stunnel-users(a)mirt.net Sent by: cc: stunnel-users-bounc Subject: [stunnel-users] Stunnel 4.05/4.07 Crash es(a)mirt.net 01/28/2005 06:28 PM Hi, I've initiated 11 stunnel processes in the same server. Each of the stunnel process has its own client certificate to communicate to application server. However after sometime of execution, the stunnel processes are crached (dying off) one by one. below is the last portion of my log (with debug level 7). I don't see any critical error in the log. Would appreciate if someone could highlight to me what cause the problem or anyone has similar experience. 2005.01.25 16:02:41 LOG7[2244:1424]: 0 server connects that finished 2005.01.25 16:02:41 LOG7[2244:1424]: 0 server renegotiatiations requested 2005.01.25 16:02:41 LOG7[2244:1424]: 486 session cache hits 2005.01.25 16:02:41 LOG7[2244:1424]: 0 session cache misses 2005.01.25 16:02:41 LOG7[2244:1424]: 0 session cache timeouts 2005.01.25 16:02:41 LOG7[2244:1424]: SSL_read returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1804]: SSL socket closed on SSL_read 2005.01.25 16:02:41 LOG5[2244:1804]: Connection closed: 716 bytes sent to SSL, 359 bytes sent to socket 2005.01.25 16:02:41 LOG7[2244:1804]: HTTP finished (7 left) 2005.01.25 16:02:41 LOG7[2244:1424]: SSL socket closed on SSL_read 2005.01.25 16:02:41 LOG5[2244:1424]: Connection closed: 716 bytes sent to SSL, 304 bytes sent to socket 2005.01.25 16:02:41 LOG7[2244:1424]: HTTP finished (6 left) 2005.01.25 16:02:41 LOG7[2244:2240]: HTTP accepted FD=516 from 10.3.5.137:1405 2005.01.25 16:02:41 LOG7[2244:2240]: FD 516 in non-blocking mode 2005.01.25 16:02:41 LOG7[2244:2240]: Creating a new thread 2005.01.25 16:02:41 LOG7[2244:2240]: New thread created 2005.01.25 16:02:41 LOG7[2244:1252]: HTTP started 2005.01.25 16:02:41 LOG5[2244:1252]: HTTP connected from 10.3.5.137:1405 2005.01.25 16:02:41 LOG7[2244:1252]: FD 704 in non-blocking mode 2005.01.25 16:02:41 LOG7[2244:1252]: HTTP connecting 10.1.11.56:443 2005.01.25 16:02:41 LOG7[2244:1252]: connect_wait: waiting 10 seconds 2005.01.25 16:02:41 LOG7[2244:1252]: connect_wait: connected 2005.01.25 16:02:41 LOG7[2244:1252]: Remote FD=704 initialized 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): before/connect initialization 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write client hello A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 read server hello A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 read finished A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write change cipher spec A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write finished A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 flush data 2005.01.25 16:02:41 LOG7[2244:1252]: 241 items in the session cache 2005.01.25 16:02:41 LOG7[2244:1252]: 979 client connects (SSL_connect()) 2005.01.25 16:02:41 LOG7[2244:1252]: 979 client connects that finished 2005.01.25 16:02:41 LOG7[2244:1252]: 489 client renegotiatations requested 2005.01.25 16:02:41 LOG7[2244:1252]: 0 server connects (SSL_accept()) 2005.01.25 16:02:41 LOG7[2244:1252]: 0 server connects that finished 2005.01.25 16:02:41 LOG7[2244:1252]: 0 server renegotiatiations requested 2005.01.25 16:02:41 LOG7[2244:1252]: 487 session cache hits 2005.01.25 16:02:41 LOG7[2244:1252]: 0 session cache misses 2005.01.25 16:02:41 LOG7[2244:1252]: 0 session cache timeouts 2005.01.25 16:02:41 LOG6[2244:1252]: SSL connected: previous session reused 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSL renegotiate ciphers 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write client hello A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_read returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_write returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_read returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_write returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_read returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 read server hello A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 read server certificate A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 read server certificate request A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 read server done A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write client certificate A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write client key exchange A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write certificate verify A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write change cipher spec A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write finished A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 flush data 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_write returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_read returned WANT_: retrying 2005.01.25 16:02:42 LOG7[2244:1252]: SSL state (connect): SSLv3 read finished A 2005.01.25 16:02:42 LOG7[2244:1252]: 242 items in the session cache 2005.01.25 16:02:42 LOG7[2244:1252]: 980 client connects (SSL_connect()) 2005.01.25 16:02:42 LOG7[2244:1252]: 980 client connects that finished 2005.01.25 16:02:42 LOG7[2244:1252]: 490 client renegotiatations requested 2005.01.25 16:02:42 LOG7[2244:1252]: 0 server connects (SSL_accept()) 2005.01.25 16:02:42 LOG7[2244:1252]: 0 server connects that finished 2005.01.25 16:02:42 LOG7[2244:1252]: 0 server renegotiatiations requested 2005.01.25 16:02:42 LOG7[2244:1252]: 487 session cache hits 2005.01.25 16:02:42 LOG7[2244:1252]: 0 session cache misses 2005.01.25 16:02:42 LOG7[2244:1252]: 0 session cache timeouts 2005.01.25 16:02:42 LOG7[2244:1252]: SSL_read returned WANT_: retrying 2005.01.25 16:02:43 LOG7[2244:2428]: s_poll_wait timeout waiting for SSL close_notify 2005.01.25 16:02:43 LOG7[2244:2284]: s_poll_wait timeout waiting for SSL close_notify 2005.01.25 16:02:43 LOG5[2244:2428]: Connection closed: 606 bytes sent to SSL, 242 bytes sent to socket 2005.01.25 16:02:43 LOG5[2244:2284]: Connection closed: 7758 bytes sent to SSL, 23278 bytes sent to socket 2005.01.25 16:02:43 LOG7[2244:2428]: HTTP finished (6 left) 2005.01.25 16:02:43 LOG7[2244:2284]: HTTP finished (5 left) 2005.01.25 16:02:45 LOG7[2244:1188]: s_poll_wait timeout waiting for SSL close_notify 2005.01.25 16:02:45 LOG5[2244:1188]: Connection closed: 1485 bytes sent to SSL, 7307 bytes sent to socket 2005.01.25 16:02:47 LOG7[2244:2228]: s_poll_wait timeout waiting for SSL close_notify 2005.01.25 16:02:47 LOG5[2244:2228]: Connection closed: 667 bytes sent to SSL, 552 bytes sent to socket 2005.01.25 16:02:49 LOG7[2244:1644]: s_poll_wait timeout waiting for SSL close_notify 2005.01.25 16:02:49 LOG5[2244:1644]: Connection closed: 667 bytes sent to SSL, 552 bytes sent to socket 2005.01.25 16:02:50 LOG7[2244:2268]: s_poll_wait timeout waiting for SSL close_notify 2005.01.25 16:02:50 LOG5[2244:2268]: Connection closed: 418 bytes sent to SSL, 1375 bytes sent to socket 2005.01.25 16:11:14 LOG7[2244:2240]: HTTP accepted FD=796 from 10.3.5.137:3973 2005.01.25 16:11:14 LOG7[2244:2240]: FD 796 in non-blocking mode 2005.01.25 16:11:14 LOG7[2244:2240]: Creating a new thread 2005.01.25 16:11:14 LOG7[2244:2240]: New thread created 2005.01.25 16:11:14 LOG7[2244:992]: HTTP started 2005.01.25 16:11:14 LOG5[2244:992]: HTTP connected from 10.3.5.137:3973 2005.01.25 16:11:14 LOG7[2244:992]: FD 632 in non-blocking mode 2005.01.25 16:11:14 LOG7[2244:992]: HTTP connecting 10.1.11.56:443 2005.01.25 16:11:14 LOG7[2244:992]: connect_wait: waiting 10 seconds 2005.01.25 16:11:14 LOG7[2244:992]: connect_wait: connected 2005.01.25 16:11:14 LOG7[2244:992]: Remote FD=632 initialized 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): before/connect initialization 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): SSLv3 write client hello A 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): SSLv3 read server hello A 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): SSLv3 read finished A 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): SSLv3 write change cipher spec A 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): SSLv3 write finished A 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): SSLv3 flush data 2005.01.25 16:11:14 LOG7[2244:992]: 242 items in the session cache 2005.01.25 16:11:14 LOG7[2244:992]: 981 client connects (SSL_connect()) 2005.01.25 16:11:14 LOG7[2244:992]: 981 client connects that finished 2005.01.25 16:11:14 LOG7[2244:992]: 490 client renegotiatations requested 2005.01.25 16:11:14 LOG7[2244:992]: 0 server connects (SSL_accept()) 2005.01.25 16:11:14 LOG7[2244:992]: 0 server connects that finished 2005.01.25 16:11:14 LOG7[2244:992]: 0 server renegotiatiations requested 2005.01.25 16:11:14 LOG7[2244:992]: 488 session cache hits 2005.01.25 16:11:14 LOG7[2244:992]: 0 session cache misses 2005.01.25 16:11:14 LOG7[2244:992]: 0 session cache timeouts 2005.01.25 16:11:14 LOG6[2244:992]: SSL connected: previous session reused 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSL renegotiate ciphers 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 write client hello A 2005.01.25 16:11:15 LOG7[2244:992]: SSL_read returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:992]: SSL_write returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:992]: SSL_read returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:992]: SSL_write returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:992]: SSL_read returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 read server hello A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 read server certificate A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 read server certificate request A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 read server done A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 write client certificate A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 write client key exchange A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 write certificate verify A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 write change cipher spec A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 write finished A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 flush data 2005.01.25 16:11:15 LOG7[2244:992]: SSL_write returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:992]: SSL_read returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:2268]: HTTP finished (5 left) thanks and rgds,spl _______________________________________________ stunnel-users mailing list stunnel-users(a)mirt.net http://stunnel.mirt.net/mailman/listinfo/stunnel-users

1 0

Stunnel 4.05/4.07 Crash
by PinLee_Su＠azuretech.com.sg 28 Jan '05

28 Jan '05

Hi, I've initiated 11 stunnel processes in the same server. Each of the stunnel process has its own client certificate to communicate to application server. However after sometime of execution, the stunnel processes are crached (dying off) one by one. below is the last portion of my log (with debug level 7). I don't see any critical error in the log. Would appreciate if someone could highlight to me what cause the problem or anyone has similar experience. 2005.01.25 16:02:41 LOG7[2244:1424]: 0 server connects that finished 2005.01.25 16:02:41 LOG7[2244:1424]: 0 server renegotiatiations requested 2005.01.25 16:02:41 LOG7[2244:1424]: 486 session cache hits 2005.01.25 16:02:41 LOG7[2244:1424]: 0 session cache misses 2005.01.25 16:02:41 LOG7[2244:1424]: 0 session cache timeouts 2005.01.25 16:02:41 LOG7[2244:1424]: SSL_read returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1804]: SSL socket closed on SSL_read 2005.01.25 16:02:41 LOG5[2244:1804]: Connection closed: 716 bytes sent to SSL, 359 bytes sent to socket 2005.01.25 16:02:41 LOG7[2244:1804]: HTTP finished (7 left) 2005.01.25 16:02:41 LOG7[2244:1424]: SSL socket closed on SSL_read 2005.01.25 16:02:41 LOG5[2244:1424]: Connection closed: 716 bytes sent to SSL, 304 bytes sent to socket 2005.01.25 16:02:41 LOG7[2244:1424]: HTTP finished (6 left) 2005.01.25 16:02:41 LOG7[2244:2240]: HTTP accepted FD=516 from 10.3.5.137:1405 2005.01.25 16:02:41 LOG7[2244:2240]: FD 516 in non-blocking mode 2005.01.25 16:02:41 LOG7[2244:2240]: Creating a new thread 2005.01.25 16:02:41 LOG7[2244:2240]: New thread created 2005.01.25 16:02:41 LOG7[2244:1252]: HTTP started 2005.01.25 16:02:41 LOG5[2244:1252]: HTTP connected from 10.3.5.137:1405 2005.01.25 16:02:41 LOG7[2244:1252]: FD 704 in non-blocking mode 2005.01.25 16:02:41 LOG7[2244:1252]: HTTP connecting 10.1.11.56:443 2005.01.25 16:02:41 LOG7[2244:1252]: connect_wait: waiting 10 seconds 2005.01.25 16:02:41 LOG7[2244:1252]: connect_wait: connected 2005.01.25 16:02:41 LOG7[2244:1252]: Remote FD=704 initialized 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): before/connect initialization 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write client hello A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 read server hello A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 read finished A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write change cipher spec A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write finished A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 flush data 2005.01.25 16:02:41 LOG7[2244:1252]: 241 items in the session cache 2005.01.25 16:02:41 LOG7[2244:1252]: 979 client connects (SSL_connect()) 2005.01.25 16:02:41 LOG7[2244:1252]: 979 client connects that finished 2005.01.25 16:02:41 LOG7[2244:1252]: 489 client renegotiatations requested 2005.01.25 16:02:41 LOG7[2244:1252]: 0 server connects (SSL_accept()) 2005.01.25 16:02:41 LOG7[2244:1252]: 0 server connects that finished 2005.01.25 16:02:41 LOG7[2244:1252]: 0 server renegotiatiations requested 2005.01.25 16:02:41 LOG7[2244:1252]: 487 session cache hits 2005.01.25 16:02:41 LOG7[2244:1252]: 0 session cache misses 2005.01.25 16:02:41 LOG7[2244:1252]: 0 session cache timeouts 2005.01.25 16:02:41 LOG6[2244:1252]: SSL connected: previous session reused 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSL renegotiate ciphers 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write client hello A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_read returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_write returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_read returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_write returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_read returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 read server hello A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 read server certificate A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 read server certificate request A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 read server done A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write client certificate A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write client key exchange A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write certificate verify A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write change cipher spec A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write finished A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 flush data 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_write returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_read returned WANT_: retrying 2005.01.25 16:02:42 LOG7[2244:1252]: SSL state (connect): SSLv3 read finished A 2005.01.25 16:02:42 LOG7[2244:1252]: 242 items in the session cache 2005.01.25 16:02:42 LOG7[2244:1252]: 980 client connects (SSL_connect()) 2005.01.25 16:02:42 LOG7[2244:1252]: 980 client connects that finished 2005.01.25 16:02:42 LOG7[2244:1252]: 490 client renegotiatations requested 2005.01.25 16:02:42 LOG7[2244:1252]: 0 server connects (SSL_accept()) 2005.01.25 16:02:42 LOG7[2244:1252]: 0 server connects that finished 2005.01.25 16:02:42 LOG7[2244:1252]: 0 server renegotiatiations requested 2005.01.25 16:02:42 LOG7[2244:1252]: 487 session cache hits 2005.01.25 16:02:42 LOG7[2244:1252]: 0 session cache misses 2005.01.25 16:02:42 LOG7[2244:1252]: 0 session cache timeouts 2005.01.25 16:02:42 LOG7[2244:1252]: SSL_read returned WANT_: retrying 2005.01.25 16:02:43 LOG7[2244:2428]: s_poll_wait timeout waiting for SSL close_notify 2005.01.25 16:02:43 LOG7[2244:2284]: s_poll_wait timeout waiting for SSL close_notify 2005.01.25 16:02:43 LOG5[2244:2428]: Connection closed: 606 bytes sent to SSL, 242 bytes sent to socket 2005.01.25 16:02:43 LOG5[2244:2284]: Connection closed: 7758 bytes sent to SSL, 23278 bytes sent to socket 2005.01.25 16:02:43 LOG7[2244:2428]: HTTP finished (6 left) 2005.01.25 16:02:43 LOG7[2244:2284]: HTTP finished (5 left) 2005.01.25 16:02:45 LOG7[2244:1188]: s_poll_wait timeout waiting for SSL close_notify 2005.01.25 16:02:45 LOG5[2244:1188]: Connection closed: 1485 bytes sent to SSL, 7307 bytes sent to socket 2005.01.25 16:02:47 LOG7[2244:2228]: s_poll_wait timeout waiting for SSL close_notify 2005.01.25 16:02:47 LOG5[2244:2228]: Connection closed: 667 bytes sent to SSL, 552 bytes sent to socket 2005.01.25 16:02:49 LOG7[2244:1644]: s_poll_wait timeout waiting for SSL close_notify 2005.01.25 16:02:49 LOG5[2244:1644]: Connection closed: 667 bytes sent to SSL, 552 bytes sent to socket 2005.01.25 16:02:50 LOG7[2244:2268]: s_poll_wait timeout waiting for SSL close_notify 2005.01.25 16:02:50 LOG5[2244:2268]: Connection closed: 418 bytes sent to SSL, 1375 bytes sent to socket 2005.01.25 16:11:14 LOG7[2244:2240]: HTTP accepted FD=796 from 10.3.5.137:3973 2005.01.25 16:11:14 LOG7[2244:2240]: FD 796 in non-blocking mode 2005.01.25 16:11:14 LOG7[2244:2240]: Creating a new thread 2005.01.25 16:11:14 LOG7[2244:2240]: New thread created 2005.01.25 16:11:14 LOG7[2244:992]: HTTP started 2005.01.25 16:11:14 LOG5[2244:992]: HTTP connected from 10.3.5.137:3973 2005.01.25 16:11:14 LOG7[2244:992]: FD 632 in non-blocking mode 2005.01.25 16:11:14 LOG7[2244:992]: HTTP connecting 10.1.11.56:443 2005.01.25 16:11:14 LOG7[2244:992]: connect_wait: waiting 10 seconds 2005.01.25 16:11:14 LOG7[2244:992]: connect_wait: connected 2005.01.25 16:11:14 LOG7[2244:992]: Remote FD=632 initialized 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): before/connect initialization 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): SSLv3 write client hello A 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): SSLv3 read server hello A 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): SSLv3 read finished A 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): SSLv3 write change cipher spec A 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): SSLv3 write finished A 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): SSLv3 flush data 2005.01.25 16:11:14 LOG7[2244:992]: 242 items in the session cache 2005.01.25 16:11:14 LOG7[2244:992]: 981 client connects (SSL_connect()) 2005.01.25 16:11:14 LOG7[2244:992]: 981 client connects that finished 2005.01.25 16:11:14 LOG7[2244:992]: 490 client renegotiatations requested 2005.01.25 16:11:14 LOG7[2244:992]: 0 server connects (SSL_accept()) 2005.01.25 16:11:14 LOG7[2244:992]: 0 server connects that finished 2005.01.25 16:11:14 LOG7[2244:992]: 0 server renegotiatiations requested 2005.01.25 16:11:14 LOG7[2244:992]: 488 session cache hits 2005.01.25 16:11:14 LOG7[2244:992]: 0 session cache misses 2005.01.25 16:11:14 LOG7[2244:992]: 0 session cache timeouts 2005.01.25 16:11:14 LOG6[2244:992]: SSL connected: previous session reused 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSL renegotiate ciphers 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 write client hello A 2005.01.25 16:11:15 LOG7[2244:992]: SSL_read returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:992]: SSL_write returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:992]: SSL_read returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:992]: SSL_write returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:992]: SSL_read returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 read server hello A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 read server certificate A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 read server certificate request A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 read server done A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 write client certificate A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 write client key exchange A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 write certificate verify A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 write change cipher spec A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 write finished A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 flush data 2005.01.25 16:11:15 LOG7[2244:992]: SSL_write returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:992]: SSL_read returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:2268]: HTTP finished (5 left) thanks and rgds,spl

2 1

Stunnel 4.05/4.07 Crash
by PinLee_Su＠azuretech.com.sg 28 Jan '05

28 Jan '05

Hi, I've initiated 11 stunnel processes in the same server. Each of the stunnel process has its own client certificate to communicate to application server. However after sometime of execution, the stunnel processes are crached (dying off) one by one. below is the last portion of my log (with debug level 7). I don't see any critical error in the log. Would appreciate if someone could highlight to me what cause the problem or anyone has similar experience. 2005.01.25 16:02:41 LOG7[2244:1424]: 0 server connects that finished 2005.01.25 16:02:41 LOG7[2244:1424]: 0 server renegotiatiations requested 2005.01.25 16:02:41 LOG7[2244:1424]: 486 session cache hits 2005.01.25 16:02:41 LOG7[2244:1424]: 0 session cache misses 2005.01.25 16:02:41 LOG7[2244:1424]: 0 session cache timeouts 2005.01.25 16:02:41 LOG7[2244:1424]: SSL_read returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1804]: SSL socket closed on SSL_read 2005.01.25 16:02:41 LOG5[2244:1804]: Connection closed: 716 bytes sent to SSL, 359 bytes sent to socket 2005.01.25 16:02:41 LOG7[2244:1804]: HTTP finished (7 left) 2005.01.25 16:02:41 LOG7[2244:1424]: SSL socket closed on SSL_read 2005.01.25 16:02:41 LOG5[2244:1424]: Connection closed: 716 bytes sent to SSL, 304 bytes sent to socket 2005.01.25 16:02:41 LOG7[2244:1424]: HTTP finished (6 left) 2005.01.25 16:02:41 LOG7[2244:2240]: HTTP accepted FD=516 from 10.3.5.137:1405 2005.01.25 16:02:41 LOG7[2244:2240]: FD 516 in non-blocking mode 2005.01.25 16:02:41 LOG7[2244:2240]: Creating a new thread 2005.01.25 16:02:41 LOG7[2244:2240]: New thread created 2005.01.25 16:02:41 LOG7[2244:1252]: HTTP started 2005.01.25 16:02:41 LOG5[2244:1252]: HTTP connected from 10.3.5.137:1405 2005.01.25 16:02:41 LOG7[2244:1252]: FD 704 in non-blocking mode 2005.01.25 16:02:41 LOG7[2244:1252]: HTTP connecting 10.1.11.56:443 2005.01.25 16:02:41 LOG7[2244:1252]: connect_wait: waiting 10 seconds 2005.01.25 16:02:41 LOG7[2244:1252]: connect_wait: connected 2005.01.25 16:02:41 LOG7[2244:1252]: Remote FD=704 initialized 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): before/connect initialization 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write client hello A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 read server hello A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 read finished A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write change cipher spec A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write finished A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 flush data 2005.01.25 16:02:41 LOG7[2244:1252]: 241 items in the session cache 2005.01.25 16:02:41 LOG7[2244:1252]: 979 client connects (SSL_connect()) 2005.01.25 16:02:41 LOG7[2244:1252]: 979 client connects that finished 2005.01.25 16:02:41 LOG7[2244:1252]: 489 client renegotiatations requested 2005.01.25 16:02:41 LOG7[2244:1252]: 0 server connects (SSL_accept()) 2005.01.25 16:02:41 LOG7[2244:1252]: 0 server connects that finished 2005.01.25 16:02:41 LOG7[2244:1252]: 0 server renegotiatiations requested 2005.01.25 16:02:41 LOG7[2244:1252]: 487 session cache hits 2005.01.25 16:02:41 LOG7[2244:1252]: 0 session cache misses 2005.01.25 16:02:41 LOG7[2244:1252]: 0 session cache timeouts 2005.01.25 16:02:41 LOG6[2244:1252]: SSL connected: previous session reused 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSL renegotiate ciphers 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write client hello A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_read returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_write returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_read returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_write returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_read returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 read server hello A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 read server certificate A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 read server certificate request A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 read server done A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write client certificate A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write client key exchange A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write certificate verify A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write change cipher spec A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write finished A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 flush data 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_write returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_read returned WANT_: retrying 2005.01.25 16:02:42 LOG7[2244:1252]: SSL state (connect): SSLv3 read finished A 2005.01.25 16:02:42 LOG7[2244:1252]: 242 items in the session cache 2005.01.25 16:02:42 LOG7[2244:1252]: 980 client connects (SSL_connect()) 2005.01.25 16:02:42 LOG7[2244:1252]: 980 client connects that finished 2005.01.25 16:02:42 LOG7[2244:1252]: 490 client renegotiatations requested 2005.01.25 16:02:42 LOG7[2244:1252]: 0 server connects (SSL_accept()) 2005.01.25 16:02:42 LOG7[2244:1252]: 0 server connects that finished 2005.01.25 16:02:42 LOG7[2244:1252]: 0 server renegotiatiations requested 2005.01.25 16:02:42 LOG7[2244:1252]: 487 session cache hits 2005.01.25 16:02:42 LOG7[2244:1252]: 0 session cache misses 2005.01.25 16:02:42 LOG7[2244:1252]: 0 session cache timeouts 2005.01.25 16:02:42 LOG7[2244:1252]: SSL_read returned WANT_: retrying 2005.01.25 16:02:43 LOG7[2244:2428]: s_poll_wait timeout waiting for SSL close_notify 2005.01.25 16:02:43 LOG7[2244:2284]: s_poll_wait timeout waiting for SSL close_notify 2005.01.25 16:02:43 LOG5[2244:2428]: Connection closed: 606 bytes sent to SSL, 242 bytes sent to socket 2005.01.25 16:02:43 LOG5[2244:2284]: Connection closed: 7758 bytes sent to SSL, 23278 bytes sent to socket 2005.01.25 16:02:43 LOG7[2244:2428]: HTTP finished (6 left) 2005.01.25 16:02:43 LOG7[2244:2284]: HTTP finished (5 left) 2005.01.25 16:02:45 LOG7[2244:1188]: s_poll_wait timeout waiting for SSL close_notify 2005.01.25 16:02:45 LOG5[2244:1188]: Connection closed: 1485 bytes sent to SSL, 7307 bytes sent to socket 2005.01.25 16:02:47 LOG7[2244:2228]: s_poll_wait timeout waiting for SSL close_notify 2005.01.25 16:02:47 LOG5[2244:2228]: Connection closed: 667 bytes sent to SSL, 552 bytes sent to socket 2005.01.25 16:02:49 LOG7[2244:1644]: s_poll_wait timeout waiting for SSL close_notify 2005.01.25 16:02:49 LOG5[2244:1644]: Connection closed: 667 bytes sent to SSL, 552 bytes sent to socket 2005.01.25 16:02:50 LOG7[2244:2268]: s_poll_wait timeout waiting for SSL close_notify 2005.01.25 16:02:50 LOG5[2244:2268]: Connection closed: 418 bytes sent to SSL, 1375 bytes sent to socket 2005.01.25 16:11:14 LOG7[2244:2240]: HTTP accepted FD=796 from 10.3.5.137:3973 2005.01.25 16:11:14 LOG7[2244:2240]: FD 796 in non-blocking mode 2005.01.25 16:11:14 LOG7[2244:2240]: Creating a new thread 2005.01.25 16:11:14 LOG7[2244:2240]: New thread created 2005.01.25 16:11:14 LOG7[2244:992]: HTTP started 2005.01.25 16:11:14 LOG5[2244:992]: HTTP connected from 10.3.5.137:3973 2005.01.25 16:11:14 LOG7[2244:992]: FD 632 in non-blocking mode 2005.01.25 16:11:14 LOG7[2244:992]: HTTP connecting 10.1.11.56:443 2005.01.25 16:11:14 LOG7[2244:992]: connect_wait: waiting 10 seconds 2005.01.25 16:11:14 LOG7[2244:992]: connect_wait: connected 2005.01.25 16:11:14 LOG7[2244:992]: Remote FD=632 initialized 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): before/connect initialization 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): SSLv3 write client hello A 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): SSLv3 read server hello A 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): SSLv3 read finished A 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): SSLv3 write change cipher spec A 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): SSLv3 write finished A 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): SSLv3 flush data 2005.01.25 16:11:14 LOG7[2244:992]: 242 items in the session cache 2005.01.25 16:11:14 LOG7[2244:992]: 981 client connects (SSL_connect()) 2005.01.25 16:11:14 LOG7[2244:992]: 981 client connects that finished 2005.01.25 16:11:14 LOG7[2244:992]: 490 client renegotiatations requested 2005.01.25 16:11:14 LOG7[2244:992]: 0 server connects (SSL_accept()) 2005.01.25 16:11:14 LOG7[2244:992]: 0 server connects that finished 2005.01.25 16:11:14 LOG7[2244:992]: 0 server renegotiatiations requested 2005.01.25 16:11:14 LOG7[2244:992]: 488 session cache hits 2005.01.25 16:11:14 LOG7[2244:992]: 0 session cache misses 2005.01.25 16:11:14 LOG7[2244:992]: 0 session cache timeouts 2005.01.25 16:11:14 LOG6[2244:992]: SSL connected: previous session reused 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSL renegotiate ciphers 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 write client hello A 2005.01.25 16:11:15 LOG7[2244:992]: SSL_read returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:992]: SSL_write returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:992]: SSL_read returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:992]: SSL_write returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:992]: SSL_read returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 read server hello A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 read server certificate A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 read server certificate request A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 read server done A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 write client certificate A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 write client key exchange A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 write certificate verify A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 write change cipher spec A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 write finished A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 flush data 2005.01.25 16:11:15 LOG7[2244:992]: SSL_write returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:992]: SSL_read returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:2268]: HTTP finished (5 left) thanks and rgds,spl

1 0

Re: [stunnel-announce] cannot create pid
by higuita 27 Jan '05

27 Jan '05

Hi On Tue, 25 Jan 2005 14:15:45 -0500 "Humberto Morell" <morell(a)seg.inf.cu> wrote: > Hello list please use the stunnel-users instead of stunnel-anounce 8) > Cannot create pid file /var/run/stunnel.pid (...) > prueba:/usr/local/etc/stunnel # ls -l /var/run (...) > chroot = /var/lib/stunnel/ (...) > pid = /var/run/stunnel.pid so you cant create the pid, and you think that /var/run is correct, but you are forgeting that you enabled the chroot, so you have to check the /var/run inside the chroot, not your main /var/run directory (that the chroot stunnel cant access) check the /var/lib/stunnel/var/run and you will find that you dont have that directory or it have the wrong permissions good luck higuita -- Daniel Mota Leite Gestor de Sistemas/System Manager Centro de Computação Gráfica Tel: +351 253 439 300 Rua Teixeira de Pascoais, 596 Fax: +351 253 439 348 4800-073 Guimarães Portugal CCG and University of Minho are Members of the INI-GraphicsNet

1 0

Hi
by UHRA 27 Jan '05

27 Jan '05

Hi, I have problem with stunnel. I like to create stunnel on my server. I want to create SSL connection on IRCD server. I am using UnrealIRCD. I have installed Stunnel 4.07 and OpenSSL 0.9.7e. I have created certificates. I use this command stunnel -c -d 6668 -r irc.myserver.sk:6697 and then when I run ircd then display me thist error: [Mon Jan 24 18:27:49 2005] - Error binding stream socket to IP 0.0.0.0 port 6668 - irc.myserver.sk[]:Address already in use Can you help me ? thanks

3 2

Profiling STunnel
by Mark Swann 26 Jan '05

26 Jan '05

All, I need to do some performance profiling on STunnel. I assume gcov and gprof are the correct tools for this. Does anyone have any experience profiling STunnel? Any advice on how to do it properly would be appreciated. Thanks Mark Swann

1 0

Cannot find License.CM file
by Ranjit Mallick 26 Jan '05

26 Jan '05

Hi , I am new to stunnel , one of the previous develoeper has developed a application using Stunnel, essentially this app will work as a proxy to outside world and tunnel back to the remote server. On the server side the Stunnel has License.cm file and when ever I bring stunnel in CMD mode, it shows a message cannot find the License.cm file(even though it is there), Obviously the License file has expired or corrupted. How do I tell this tunnel.exe not to look for that file or how can I generate a license file(.cm)? Pls note that the tunnel has all the required files in it's directory tunnel.pem,tunnel.conf,ssleay32.dll,libeay32.dll,ssleay32.exp), pls help this is a show stopper and is effecting the client.Any leads or direction will be much appreciated. Thank you Ranjit __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

win32 stunnel - quiet service install
by joe smith 22 Jan '05

22 Jan '05

I would like to request the following feature be included in subsequent releases of stunnel. Cheers, Jeff Greetings, It would be great if while installing as a service on win32, there was an option to install quietly - i.e. only pop up a dialog box to the user if there's a problem. Any chance of somebody nice compiling me a binary that does this? :) M. -- Michael Brown {0x527670C0} | `One of the main causes of the fall of Systems Administrator | the Roman Empire was that, lacking zero, +1 519 888 7111 x2339 | they had no way to indicate successful michaelb at opentext.com | termination of their C programs.' - Firth --------------------------------- Do you Yahoo!? Yahoo! Search presents - Jib Jab's 'Second Term'

2 1

stunnel and verify
by Brian Hirt 21 Jan '05

21 Jan '05

Hi, I've recently set up stunnel for a remote vnc connection, and it's working great. However, I would like to restrict access based on cert (only allow access a single public key), because nobody else should be accessing it besides my one machine. It seems what i want is to set verify = 3, but I'm using self-signed certs on my client, so verify = 3 fails. Is there some way to verify the client public key without doing the self signed test too? I'm sorry if this is a faq -- i searched the lists and read the faq and couldn't find anything. Thanks! (I'm running stunnel 4.04 on fedora1, and stunnel 4.04 on mac 10.3.7, installed via fink) my stunnel.conf is pretty simple. client conf is (sans connection info) client = yes cert = /sw/etc/stunnel/stunnel.pem chroot = /var/run/stunnel/ pid = /stunnel.pid setuid = stunnel setgid = stunnel server conf is: client = no cert = /etc/stunnel/stunnel.pem CApath = /etc/stunnel/clientdb chroot = /var/run/stunnel/ verify=3 pid = /stunnel.pid setuid = stunnel setgid = stunnel -------------------------------------------- MobyGames http://www.mobygames.com The world's largest and most comprehensive gaming database project

1 0

Re: [stunnel-users] Activating Stunnel After Exiting (Newbie)
by Andre Tertling 20 Jan '05

20 Jan '05

[...] >Pack 2.) After close Agent, I right-click the Stunnel icon on the task >bar and choose Exit. If I try to activate Stunnel later, by >double-clicking its desktop icon, I am presented with an error window >headed "stunnel 4.07 on Win32" with the following message: "Failed to >create a new service". Looking at Properties on the desktop, I see that >the Target is "C:\stunnel\stunnel-4.07.exe -install". This looks wrong, >as it appears to be the option for initial installation of the program. I >assume I need to change this, or discover another method of re- [...] You already found the culprit. The command line option "-install" attempts to install the stunnel service. As it is already present in the services list, this has to fail. You can easily start and stop stunnel using the net command from a command line window: net start stunnel to start stunnel, or: net stop stunnel to shut it down again. You could make up a batch file to launch stunnel automatically for the time agent is running: --file runagent.cmd begin-- @echo off net stunnel start C:\Program Files\Agent!\Agent32.exe net stunnel stop --file runagent.cmd end-- Just edit the path for agent32.exe to match the path where you have Forté Agent installed, and you're done. P.S. I know net stunnel start can complain about that the service is already running, but that's just cosmetical and I was too lazy to implement logic to check if the service is already running ;) Best regards, Andre

1 1

Activating Stunnel After Exiting (Newbie)
by mhrtmhd94＠att.net 20 Jan '05

20 Jan '05

Hi. I just installed Stunnel, in order to be able to continue Agent as my mews reader. This works well. Based on the cautions on the website, I have decided to keep Stunnel active only when I am using Agent. Stunnel opens when I boot Windows - (XP Home Edition with Service Pack 2.) After close Agent, I right-click the Stunnel icon on the task bar and choose Exit. If I try to activate Stunnel later, by double-clicking its desktop icon, I am presented with an error window headed "stunnel 4.07 on Win32" with the following message: "Failed to create a new service". Looking at Properties on the desktop, I see that the Target is "C:\stunnel\stunnel-4.07.exe -install". This looks wrong, as it appears to be the option for initial installation of the program. I assume I need to change this, or discover another method of re-opening stunnel. As it stands now, I have to reboot to accomplish this. Any assistance will be appreciated. Thanks.

1 0

stunnel-users@mirt.net
by eric wyzerski 17 Jan '05

17 Jan '05

Hi, Im trying to bind my 465 port tu my 25 port to have a ssl-smtp with the following command: stunnel -p /etc/stunnel.pem2 -d 465 -r localhost:25 However when I try to connect to port 465, I get the following error, stunnel[3443]: SSL_accept: Peer suddenly disconnected Any idea? Thank you Eric _________________________________________________________________ Take advantage of powerful junk e-mail filters built on patented Microsoft® SmartScreen Technology. http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=ht… Start enjoying all the benefits of MSN® Premium right now and get the first two months FREE*.

2 1

Problem with zlib compression
by Allan Guild 13 Jan '05

13 Jan '05

I'm having problems with zlib compression - stunnel 4.07 on my client machne crashes whenever I try and start a session. With compression set to rle or not defined, there is no problem. I am securing a MySQL connection between a Windows client and Mandrake Linux 10.1 server. Client Configuration: Stunnel 4.07 and openssl 0.9.7e-zlib binaries downloaded from Stunnel website stunnel.conf ------------ cert=./Allan_Guild_Work.pem key=./Allan_Guild_Work_key.pem client=yes compression=zlib [Primary Club] accept=3306 connect=195.137.78.107:3307 TIMEOUTbusy=5 ------------- Server Configuration: Stunnel 4.07 and openssl 0.9.7e (compiled with zlib support) rebuilt from Mandrake Cooker SRPMS stunnel.conf ------------ CApath=/etc/ssl/stunnel/certs/ cert=/etc/ssl/stunnel/CAcert.pem key=/etc/ssl/stunnel/CAkey.pem client=no foreground=yes pid=/var/run/stunnel.pid verify=0 compression=zlib [Primary Club] accept=3307 connect=3306 ------------ When I try and connect, I get the following output from the client (which then crashes): ------------- 2005.01.11 19:04:14 LOG5[308:2172]: stunnel 4.07 on x86-pc-mingw32-gnu WIN32+IPv4 with OpenSSL 0.9.7e 25 Oct 2004 2005.01.11 19:04:14 LOG5[308:1688]: No limit detected for the number of clients 2005.01.11 19:04:16 LOG5[308:804]: Primary Club connected from 127.0.0.1:4769 ------------- and the following from the server: ------------- 2005.01.11 19:21:30 LOG5[25439:1076523680]: stunnel 4.07 on i586-mandrake-linux-gnu PTHREAD+POLL+IPv4+LIBWRAP with OpenSSL 0.9.7e 25 Oct 2004 2005.01.11 19:21:30 LOG5[25439:1076523680]: 500 clients allowed 2005.01.11 19:21:53 LOG5[25439:1073900464]: Primary Club connected from 212.135.219.66:3974 2005.01.11 19:21:53 LOG5[25439:1073900464]: VERIFY IGNORE: depth=0, /C=UK/ST=Some-State/L=London/O=Primary Club/CN=Allan Guild/emailAddress=allan.guild(a)bitsnpieces.org.uk 2005.01.11 19:21:53 LOG5[25439:1073900464]: VERIFY IGNORE: depth=0, /C=UK/ST=Some-State/L=London/O=Primary Club/CN=Allan Guild/emailAddress=allan.guild(a)bitsnpieces.org.uk 2005.01.11 19:21:57 LOG3[25439:1073900464]: SSL_read (ERROR_SYSCALL): Connection reset by peer (104) 2005.01.11 19:21:57 LOG5[25439:1073900464]: Connection reset: 3843 bytes sent to SSL, 55 bytes sent to socket ------------- Any advice would be greatly appreciated (Do I need a zlib dll?), Allan

2 2

stunnel dropping connection with media wiki
by christopher＠baus.net 12 Jan '05

12 Jan '05

Hi all, I've been using stunnel with SMTP, IMAP, and HTTP with out a problem. Yesterday I installed media wiki on Fedora Core 2 w/ Apache. It works fine if I access it directly, but if I access the site via stunnel, the proxy drops connection. I was wondering if anybody else has seen this type of problem. I am tempted to dig into it, but I am honestly short on time right now. I think it might have something to do with the redirects that Media wiki uses, but that's just a wild guess. Christopher Baus ======== Implementing an HTTP proxy? Consider a fast, secure alternative http://www.baus.net/ads/license

1 0

Re: [stunnel-users] OpenSSL - write:errno=131
by Hans Werner Strube 11 Jan '05

11 Jan '05

> (BTW, I use here the word "managed" becuase it was not straightforward: the > up-to-date version - 4.07 - wouldn't compile under Solaris.) For this special problem, try my patch from 04 Jan 05 in this list, Subject: stunnel-4.07 on non-IPv6 systems

1 0

openssl and a pkcs#11 device
by Edward 11 Jan '05

11 Jan '05

Hello, Has anyone ever tried to build stunnel using openssl with a pkcs#11 crypto device? Regards, Edward Stempel -- "The responsibility of a citizen is to keep his mouth open." - Gunther Grass

1 0

OpenSSL - write:errno=131
by Andrzej Marecki 11 Jan '05

11 Jan '05

I managed to compile and install stunnel 4.06 under Solaris 2.6. (BTW, I use here the word "managed" becuase it was not straightforward: the up-to-date version - 4.07 - wouldn't compile under Solaris.) My stunnel.conf file reads: cert=/opt/etc/stunnel/pop3.pem chroot = /opt/var/stunnel/ setuid = nobody setgid = nogroup pid = /stunnel.pid output=/var/log/stunnel.log client = no [spop3] accept = localhost:995 connect = localhost:110 [ssmtp] accept = localhost:465 connect = localhost:25 -------------- /opt/etc/stunnel/pop3.pem has been set up according the instructions at: http://www.freebsd.hello.pl/files/modules.php?name=News&file=article&sid=5 ...so I do hope it's OK ;-). Anyway, stunnel daemon works - what I get in stunnel.log reads: stunnel 4.06 on sparc-sun-solaris2.6 PTHREAD+POLL with OpenSSL 0.9.7e 25 Oct 2004 29 clients allowed (Date & time of the messages quoted above are omitted.) Now I try to test stunnel: #/opt/bin/openssl s_client -connect localhost:995 -prexit ...and what I get is: CONNECTED(00000003) write:errno=131 --- no peer certificate available --- No client certificate CA names sent --- SSL handshake has read 0 bytes and written 148 bytes --- New, (NONE), Cipher is (NONE) --------------- I get the same when "openssl s_client -connect localhost:995" is issued by a non-privileged user. Needless to say I can't connect to port 995 using a bone fide MUA running on a PC under M$W (Thunderbird to be exact). Can you help me, please. Andrzej -- ----------------------------------------------------------------------------- Andrzej Marecki | Torun Centre for Astronomy | e-mail: amr(a)astro.uni.torun.pl N. Copernicus University | WWW: http://www.astro.uni.torun.pl ul. Gagarina 11 | tel: +48 56 6113032 PL-87-100 Torun, POLAND | fax: +48 56 6113009 ----------------------------------------------------------------------------- "If Bill Gates actually had to admin his own stuff, he'd shoot himself." -----------------------------------------------------------------------------

1 0

RE: [stunnel-users] Stunnel and DistCache Patch
by Kling, Kent M. 10 Jan '05

10 Jan '05

autoconf-2.13-14 was my installed version. I upgraded to autoconf-2.53-8 and it now works. Thanks for helping out. Kent -----Original Message----- From: Peter Pentchev [mailto:roam@ringlet.net] Sent: Monday, January 10, 2005 8:08 AM To: Senthil Prabu.S Cc: Kling, Kent M.; stunnel-users(a)mirt.net Subject: Re: [stunnel-users] Stunnel and DistCache Patch On Mon, Jan 10, 2005 at 11:05:19AM +0530, Senthil Prabu.S wrote: > The problem is that,since the patch you applied have modified the configure.ac file, a brand new configure script should be generated to reflect the change done at the configure.ac. So run "autoconf" command to produce new configure script. > > This will solve your problem. Well, it... depends :) The original poster mentions that when he ran autoconf, he got an error stating that configure.in could not be found. This might mean that he's running an older version of autoconf, one that only looks for configure.in, not configure.ac. Kent, what does 'rpm -qa | fgrep auto' tell you? G'luck, Peter -- Peter Pentchev roam(a)ringlet.net roam(a)cnsys.bg roam(a)FreeBSD.org PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 I am the meaning of this sentence. This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information of Transaction Network Services.Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

stunnel-users