May 2007 - stunnel-users

Plz help the n00b (syslog-ng & stunnel)
by F.M. Taylor 31 May '07

31 May '07

Greetings all. Seemed simple enough, but I can seem to get it to work. I have obviously missed something simple. Here is the info you will need (and probably some you won't). I have tried every combination of options I can think of, and I have searched the archives and the web. It looks like it is almost working, but the server I am trying to connect to never sees the data (however "they" have it working on "their" systems, so it must be me). "They" say it connects, talks a little, no real data xfer, closes, then more data (followed by the obligatory TCP_RSTs for dead connects). [insert begging] [root@bofh stunnel-4.20]# stunnel /etc/stunnel/stunnel.conf 2007.05.25 10:43:00 LOG7[20728:182894198944]: Snagged 64 random bytes from /root/.rnd 2007.05.25 10:43:00 LOG7[20728:182894198944]: Wrote 1024 new random bytes to /root/.rnd 2007.05.25 10:43:00 LOG7[20728:182894198944]: RAND_status claims sufficient entropy for the PRNG 2007.05.25 10:43:00 LOG7[20728:182894198944]: PRNG seeded successfully 2007.05.25 10:43:00 LOG7[20728:182894198944]: Configuration SSL options: 0x00000FFF 2007.05.25 10:43:00 LOG7[20728:182894198944]: SSL options set: 0x00000FFF 2007.05.25 10:43:00 LOG7[20728:182894198944]: SSL context initialized for service 5140 [root@bofh stunnel-4.20]# tail -f /var/log/stunnel4/stunnel.log 2007.05.25 10:43:00 LOG5[20728:182894198944]: Threading:PTHREAD SSL:ENGINE Sockets:POLL,IPv4 Auth:LIBWRAP 2007.05.25 10:43:00 LOG6[20728:182894198944]: file ulimit = 1024 (can be changed with 'ulimit -n') 2007.05.25 10:43:00 LOG6[20728:182894198944]: poll() used - no FD_SETSIZE limit for file descriptors 2007.05.25 10:43:00 LOG5[20728:182894198944]: 500 clients allowed 2007.05.25 10:43:00 LOG7[20728:182894198944]: FD 4 in non-blocking mode 2007.05.25 10:43:00 LOG7[20728:182894198944]: FD 5 in non-blocking mode 2007.05.25 10:43:00 LOG7[20728:182894198944]: FD 6 in non-blocking mode 2007.05.25 10:43:00 LOG7[20728:182894198944]: SO_REUSEADDR option set on accept socket 2007.05.25 10:43:00 LOG7[20728:182894198944]: 5140 bound to 127.0.0.1:5140 2007.05.25 10:43:00 LOG7[20729:182894198944]: Created pid file /var/run/stunnel4/stunnel.pid 2007.05.25 10:43:29 LOG7[20729:182894198944]: 5140 accepted FD=7 from 127.0.0.1:64820 2007.05.25 10:43:29 LOG7[20729:1073809760]: 5140 started 2007.05.25 10:43:29 LOG7[20729:1073809760]: FD 7 in non-blocking mode 2007.05.25 10:43:29 LOG7[20729:1073809760]: TCP_NODELAY option set on local socket 2007.05.25 10:43:29 LOG7[20729:1073809760]: FD 8 in non-blocking mode 2007.05.25 10:43:29 LOG7[20729:1073809760]: FD 9 in non-blocking mode 2007.05.25 10:43:29 LOG7[20729:1073809760]: Connection from 127.0.0.1:64820 permitted by libwrap 2007.05.25 10:43:29 LOG7[20729:182894198944]: Cleaning up the signal pipe 2007.05.25 10:43:29 LOG5[20729:1073809760]: 5140 accepted connection from 127.0.0.1:64820 2007.05.25 10:43:29 LOG6[20729:182894198944]: Child process 20748 finished with code 0 2007.05.25 10:43:29 LOG7[20729:1073809760]: FD 8 in non-blocking mode 2007.05.25 10:43:29 LOG7[20729:1073809760]: 5140 connecting xxx.xxx.xxx.xxx:5140 2007.05.25 10:43:29 LOG7[20729:1073809760]: connect_wait: waiting 10 seconds 2007.05.25 10:43:29 LOG7[20729:1073809760]: connect_wait: connected 2007.05.25 10:43:29 LOG5[20729:1073809760]: 5140 connected remote server from 192.168.2.23:64821 2007.05.25 10:43:29 LOG7[20729:1073809760]: Remote FD=8 initialized 2007.05.25 10:43:29 LOG7[20729:1073809760]: TCP_NODELAY option set on remote socket 2007.05.25 10:43:29 LOG7[20729:1073809760]: SSL state (connect): before/connect initialization 2007.05.25 10:43:29 LOG7[20729:1073809760]: SSL state (connect): SSLv3 write client hello A 2007.05.25 10:43:29 LOG7[20729:1073809760]: SSL state (connect): SSLv3 read server hello A 2007.05.25 10:43:29 LOG7[20729:1073809760]: SSL state (connect): SSLv3 read server certificate A 2007.05.25 10:43:29 LOG7[20729:1073809760]: SSL state (connect): SSLv3 read server done A 2007.05.25 10:43:29 LOG7[20729:1073809760]: SSL state (connect): SSLv3 write client key exchange A 2007.05.25 10:43:29 LOG7[20729:1073809760]: SSL state (connect): SSLv3 write change cipher spec A 2007.05.25 10:43:29 LOG7[20729:1073809760]: SSL state (connect): SSLv3 write finished A 2007.05.25 10:43:29 LOG7[20729:1073809760]: SSL state (connect): SSLv3 flush data 2007.05.25 10:43:29 LOG7[20729:1073809760]: SSL state (connect): SSLv3 read finished A 2007.05.25 10:43:29 LOG7[20729:1073809760]: 1 items in the session cache 2007.05.25 10:43:29 LOG7[20729:1073809760]: 1 client connects (SSL_connect()) 2007.05.25 10:43:29 LOG7[20729:1073809760]: 1 client connects that finished 2007.05.25 10:43:29 LOG7[20729:1073809760]: 0 client renegotiations requested 2007.05.25 10:43:29 LOG7[20729:1073809760]: 0 server connects (SSL_accept()) 2007.05.25 10:43:29 LOG7[20729:1073809760]: 0 server connects that finished 2007.05.25 10:43:29 LOG7[20729:1073809760]: 0 server renegotiations requested 2007.05.25 10:43:29 LOG7[20729:1073809760]: 0 session cache hits 2007.05.25 10:43:29 LOG7[20729:1073809760]: 0 session cache misses 2007.05.25 10:43:29 LOG7[20729:1073809760]: 0 session cache timeouts 2007.05.25 10:43:29 LOG6[20729:1073809760]: SSL connected: new session negotiated 2007.05.25 10:43:29 LOG6[20729:1073809760]: Negotiated ciphers: AES256-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA1 2007.05.25 10:43:29 LOG7[20729:1073809760]: SSL alert (read): warning: close notify 2007.05.25 10:43:29 LOG7[20729:1073809760]: SSL closed on SSL_read 2007.05.25 10:43:29 LOG7[20729:1073809760]: Socket write shutdown 2007.05.25 10:43:29 LOG7[20729:1073809760]: SSL write shutdown 2007.05.25 10:43:29 LOG7[20729:1073809760]: SSL alert (write): warning: close notify 2007.05.25 10:43:29 LOG6[20729:1073809760]: SSL_shutdown successfully sent close_notify 2007.05.25 10:43:29 LOG5[20729:1073809760]: Connection closed: 303 bytes sent to SSL, 0 bytes sent to socket 2007.05.25 10:43:29 LOG7[20729:1073809760]: 5140 finished (0 left) /etc/stunnel/stunnel.conf setuid = stunnel4 setgid = stunnel4 pid = /var/run/stunnel4/stunnel.pid socket = l:TCP_NODELAY=1 socket = r:TCP_NODELAY=1 debug = 7 output = /var/log/stunnel4/stunnel.log [5140] client = yes options = ALL accept = 127.0.0.1:5140 connect = xxx.xxx.xxx.xxx:5140 [root@bofh stunnel-4.20]# tail /var/log/syslog May 25 10:57:35 bofh syslog-ng[1926]: EOF occurred while idle; fd='11' May 25 10:57:35 bofh syslog-ng[1926]: Connection broken; time_reopen='60' May 25 10:58:37 bofh syslog-ng[1926]: EOF occurred while idle; fd='11' May 25 10:58:37 bofh syslog-ng[1926]: Connection broken; time_reopen='60' May 25 10:59:38 bofh syslog-ng[1926]: EOF occurred while idle; fd='11' May 25 10:59:38 bofh syslog-ng[1926]: Connection broken; time_reopen='60' -- ......\\|//........^^^^^........)))((........%%%%%........,,,,,...... ......(- -)........(o o)........(- o)........(0-0)........(* *)...... +--ooO-(_)-Ooo--oo0-(_)-0oo--ooO-(_)-Ooo--oo0-(_)-0oo--ooO-(_)-Ooo--+ | F.M. (Mike) Taylor........'Recedite, plebes! Gero rem imperialem!'| | 'Ecce potestas casei'..............GIAC GSEC & GCFW Certified.....| | Desk: 4-1872...........................C: 812-841-1876............| +-------------------------------------------------------------------+

1 2

Please help in difficulty in debugging the Stunnel code
by piyush tewari 31 May '07

31 May '07

Hello Friends, I am facing problems in debugging the source code of stunnel. When i debug line no 1266 of the options.c , that is "name=default_config_file;" , the df pointer gets it's value that means it is executing another line , line no 1305 of options.c itself "df=file_open(name, 0);". I am not getting this working of the stunnel code. And the other problem that i m facing is that during the debugging , many variables are not showing their occupied value. So please help me in understanding this working and resolving it. Thank you very much in advance for this help. warm regards Pkt --------------------------------- Get the free Yahoo! toolbar and rest assured with the added security of spyware protection.

1 0

stunnel-4.20 server loop on AIX 5.3
by Peter Heimann 28 May '07

28 May '07

Under heavy usage, stunnel-4.20 on AIX 5.3 enters into a loop with high CPU load. Test setup: client ------------> gateway ------------> server ApacheBench 2.0.40-dev stunnel-4.20 Apache 1.3 in server mode OpenSSL 0.9.8d stunnel 4.20 on powerpc-ibm-aix5.3.0.0 with OpenSSL 0.9.8d 28 Sep 2006 Threading:PTHREAD SSL:ENGINE Sockets:POLL,IPv4 ; stunnel configuration file, server mode cert = /etc/stunnel.pem setuid = stunnel setgid = stunnel pid = /tmp/stunnel.pid debug = local3.notice output = /tmp/stunnel.log [https] accept = gateway:4433 connect = server:80 The first client requests are processed without error, then some connections fail: % ab -n 1000 -c 70 https://gateway:4433/ This is ApacheBench, Version 2.0.40-dev <$Revision: 1.146 $> apache-2.0 [...] Test aborted after 10 failures Apr_socket_connect(): Invalid argument (22) Total of 705 requests completed One or more connections stay in state CLOSE_WAIT, and stunnel is chewing away CPU cycles (CPU usage >99%). % lsof -a -i -c stunnel COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME stunnel 196856 stunnel 6u IPv4 0xf100020002feeb98 0t0 TCP gateway:4433 (LISTEN) stunnel 196856 stunnel 46u IPv4 0xf100020002e98398 0t0 TCP gateway:4433 ->server:50271 (CLOSE_WAIT) In this state, attaching a debugger shows that stunnel is stuck in a loop in init_ssl() within client.c: +321 while(1) { +322 if(c->opt->option.client) +323 i=SSL_connect(c->ssl); +324 else +325 i=SSL_accept(c->ssl); +326 err=SSL_get_error(c->ssl, i); /* err==5 */ /* ... */ +349 if(err==SSL_ERROR_SYSCALL) { +350 switch(get_last_socket_error()) { +351 case EINTR: +353 case EAGAIN: /* loop continues */ +354 continue; +355 } +356 } SSL_accept() returns with error, SSL_get_error() returns 5 (SSL_ERROR_SYSCALL). get_last_socket_error() returns EAGAIN, and the loop continues without end. Nevertheless, new connection requests still get processed. Even before CPU usage goes up, for every new connection, SSL_accept() results in SSL_ERROR_SYSCALL for 20 to 1800 times before finally data is exchanged. stunnel enters this endless loop on AIX both with OpenSSL 0.9.8d and OpenSSL 0.9.8e. If I replace the AIX gateway machine with one running stunnel-4.20 on Solaris, I do not experience any problems. What might trigger this loop on AIX 5.3? How can it be avoided? -- Peter Heimann _______________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192

1 0

Reconfiguration while running
by James Moe 27 May '07

27 May '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, Does Stunnel offer a way to reload the configuration file? Usually that is done with SIGHUP but the code looks like it just terminates. Does it have a way to sense that the conf has changed and reloads it? Or must Stunnel be terminated and restarted? - -- jimoe (at) sohnen-moe (dot) com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (OS/2) iD8DBQFGWhbJzTcr8Prq0ZMRAoy8AJ4ocDWfBEvEfoIYoypURg2hTxUh0gCfajo1 nVXpKD5iBFEx6ZHauPemnsU= =vGul -----END PGP SIGNATURE-----

1 0

Quick question relating to end to end encryption with hapoxy:
by lists 27 May '07

27 May '07

I'm using stunnel to decrypt HTTPS and pass it to HAPROXY to insert a cookie and it works very well and very fast. Is their a way of making HAPROXY talk to the backend servers in HTTPS? i.e.. End to end encryption. Can I re-direct it back through stunnel in reverse? Thanks in advance, Malcolm.

2 1

Brocken Connections
by Manfred Alfaré 25 May '07

25 May '07

Hi! I have some trouble using STUNNEL on WIN98 to secure connections to HFS (Http File Server), and hope, somebody can help me. I can connect to HFS with the Browser (Firefox 2.0.0.3, IE 6.0, on the same machine HFS is running, an other one in LAN and a third via internet) and download files, bat every downloaded File is corrupt. In most cases, transfer seems to terminate normally, but the downloaded file ist to short, sometimes there is popup, that tells me, that the file could not be read, because the connection is broken. The log file shows the following: ********************************* stunnel 4.20 on x86-pc-mingw32-gnu with OpenSSL 0.9.8d 28 Sep 2006 Threading:WIN32 SSL:ENGINE Sockets:SELECT,IPv4 No limit detected for the number of clients https accepted connection from 85.127.28.154:63819 https connected remote server from 127.0.0.1:1287 Connection closed: 1632 bytes sent to SSL, 476 bytes sent to socket https accepted connection from 85.127.28.154:63821 https accepted connection from 85.127.28.154:63823 https connected remote server from 127.0.0.1:1290 https connected remote server from 127.0.0.1:1291 Connection closed: 919 bytes sent to SSL, 349 bytes sent to socket Connection closed: 720 bytes sent to SSL, 402 bytes sent to socket https accepted connection from 85.127.28.154:63825 https accepted connection from 85.127.28.154:63827 https connected remote server from 127.0.0.1:1294 https connected remote server from 127.0.0.1:1295 Connection closed: 715 bytes sent to SSL, 402 bytes sent to socket Connection closed: 277 bytes sent to SSL, 402 bytes sent to socket https accepted connection from 85.127.28.154:63829 https connected remote server from 127.0.0.1:1297 Connection closed: 269 bytes sent to SSL, 402 bytes sent to socket https accepted connection from 85.127.28.154:63831 https connected remote server from 127.0.0.1:1299 Connection closed: 920 bytes sent to SSL, 349 bytes sent to socket https accepted connection from 85.127.28.154:63833 https connected remote server from 127.0.0.1:1301 https accepted connection from 85.127.28.154:63835 https connected remote server from 127.0.0.1:1303 Connection closed: 920 bytes sent to SSL, 349 bytes sent to socket readsocket: Connection reset by peer (WSAECONNRESET) (10054) Connection reset: 1289938 bytes sent to SSL, 481 bytes sent to socket ************************* My STUNNEL.CONF looks like this: ******************************** ; File with certificate and private key cert = stunnel.pem key = stunnel.pem ; Log (1= minimal, 5=recommended, 7=all) and log file) ; Preceed with a ";" to disable logging debug = 5 output = stunnel.log ; Some performance tuning socket = l:TCP_NODELAY=1 socket = r:TCP_NODELAY=1 ; Data compression algorithm: zlib or rle compression = zlib ; SSL bug options / NO SSL:v2 (SSLv3 and TLSv1 is enabled) options = ALL options = NO_SSLv2 ; Service-level configuration ; Stunnel listens to port 443 (HTTPS) to any IP ; and connects to port 44300 (HFS) on localhost [https] accept = 0.0.0.0:443 connect = 127.0.0.1:44300 TIMEOUTclose = 0 ************************************* Your help will be appreciated. Regards Manfred Alfare (not a native englisch speaker :-(

1 0

Re: [stunnel-users] stunnel-users Digest, Vol 34, Issue 5
by GNUtoo＠no-log.org 23 May '07

23 May '07

> >>> in cygwin i have the following errors: >>> $ openssl req -new -x509 -days 365 -nodes -config >>> /etc/stunnel/stunnel.conf -out stunnel.pem -keyout stunnel.pem >>> Generating a 512 bit RSA private key >>> ..++++++++++++ >>> .....++++++++++++ >>> writing new private key to 'stunnel.pem' >>> ----- >>> unable to find 'distinguished_name' in config >>> problems making Certificate Request >>> 1988:error:0E06D06C:configuration file routines:NCONF_get_string:no >>> value:conf_lib.c:329:group=req name=distinguished_name >>> >>> $ /usr/bin/stunnel.exe >>> 2007.05.13 22:37:12 LOG4[2188:6422536]: Wrong permissions on >>> /etc/stunnel/mail.pem >>> 2007.05.13 22:37:12 LOG3[2188:6422536]: Error reading certificate file: >>> /etc/stunnel/stunnel.pem >>> 2007.05.13 22:37:12 LOG3[2188:6422536]: error stack: 140DC009 : >>> error:140DC009:SSL routines:SSL_CTX_use_certificate_chain_file:PEM lib >>> 2007.05.13 22:37:12 LOG3[2188:6422536]: >>> SSL_CTX_use_certificate_chain_file: 906D06C: error:0906D06C:PEM >>> routines:PEM_read_bio:no start line >>> >>> and i ran all as Administrator >> >> Can you please post your /etc/stunnel/stunnel.conf, and also the results >> of >> 'ls -al /etc/stunnel'. Thanks, Andrew. >> > $ ls -al /etc/stunnel/ > total 6 > drwx------+ 2 FC1 Users 0 May 13 22:37 . > drwx------+ 11 FC1 Users 0 May 13 21:56 .. > lrwxrwxrwx 1 Administrator Nessuno 11 May 13 22:37 mail.pem -> > stunnel.pem > -rwx------ 1 Administrator Nessuno 1578 May 13 22:36 stunnel.conf > -rwx------+ 1 FC1 Users 1533 May 13 22:13 stunnel.conf-sample > -rw-r--r-- 1 Administrator Nessuno 497 May 13 22:36 stunnel.pem > > > $ cat /etc/stunnel/stunnel.conf > #; Sample stunnel configuration file by Michal Trojnara 2002-2006 > #; Some options used here may not be adequate for your particular > configuration > #; Please make sure you understand them (especially the effect of chroot > jail) > > #; Certificate/key is needed in server mode and optional in client mode > #;cert = /etc/stunnel/mail.pem > key = /etc/stunnel/mail.pem > > #; Protocol version (all, SSLv2, SSLv3, TLSv1) > sslVersion = SSLv3 > > #; Some security enhancements for UNIX systems - comment them out on Win32 > chroot = /var/lib/stunnel/ > setuid = nobody > setgid = nobody > #; PID is created inside chroot jail > pid = /stunnel.pid > > #; Some performance tunings > socket = l:TCP_NODELAY=1 > socket = r:TCP_NODELAY=1 > #;compression = rle > > #; Workaround for Eudora bug > #;options = DONT_INSERT_EMPTY_FRAGMENTS > > #; Authentication stuff > #;verify = 2 > #; Don't forget to c_rehash CApath > #; CApath is located inside chroot jail > #;CApath = /certs > #; It's often easier to use CAfile > #;CAfile = /etc/stunnel/certs.pem > #; Don't forget to c_rehash CRLpath > #; CRLpath is located inside chroot jail > #;CRLpath = /crls > #; Alternatively you can use CRLfile > #;CRLfile = /etc/stunnel/crls.pem > > #; Some debugging stuff useful for troubleshooting > #;debug = 7 > #;output = stunnel.log > > #; Use it for client mode > #;client = yes > > #; Service-level configuration > > #;[pop3s] > #;accept = 995 > #;connect = 110 > > #;[imaps] > #;accept = 993 > #;connect = 143 > > #;[ssmtp] > #;accept = 465 > #;connect = 25 > > #;[https] > ##;accept = 443 > #;connect = 80 > #;TIMEOUTclose = 0 > > #; vim:ft=dosini > > [vnc] > accept = 127.0.0.1:5500 > connect = 192.168.1.107:443 now that i have posted the config file...do i need to post something else?

2 1

Re: [stunnel-users] Simple SMTP encryption
by Hans Werner Strube 21 May '07

21 May '07

James Moe wrote: > client = yes > > [smtps] > accept = 127.0.0.1:465 > connect = smtpauth.earthlink.net:25 > > I missed the part somewhere that tells Stunnel to issue a STARTTLS to > the smtp server before attempting to negotiate a TLS connection. Add (under [smtps]): protocol = smtp

1 0

Simple SMTP encryption
by James Moe 19 May '07

19 May '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hello, stunnel 4.20 with OpenSSL 0.9.8d 28 Sep 2006 I wish have my MUA to send messages encrypted to a secure mail server. Stunnel is set up as a client with the following configuration: client = yes [smtps] accept = 127.0.0.1:465 connect = smtpauth.earthlink.net:25 I missed the part somewhere that tells Stunnel to issue a STARTTLS to the smtp server before attempting to negotiate a TLS connection. The "failed handshake" bit is because the server is rejecting the command because of NULLs in the text stream. 501 NULL characters are not allowed in SMTP commands. Then there is the "wrong version" error. I suppose that is a side effect of the handshake failure? Here is a typical connection log: 2007.05.19 12:52:42 LOG7[232:4239]: smtps accepted FD=12 from 127.0.0.1:52672 2007.05.19 12:52:42 LOG7[232:4239]: Creating a new thread 2007.05.19 12:52:42 LOG7[232:4239]: New thread created 2007.05.19 12:52:42 LOG7[264:4239]: smtps started 2007.05.19 12:52:42 LOG7[264:4239]: FD 12 in non-blocking mode 2007.05.19 12:52:42 LOG7[264:4239]: TCP_NODELAY option set on local socket 2007.05.19 12:52:42 LOG5[264:4239]: smtps accepted connection from 127.0.0.1:52672 2007.05.19 12:52:42 LOG7[264:4239]: FD 15 in non-blocking mode 2007.05.19 12:52:42 LOG7[264:4239]: smtps connecting 207.69.189.201:25 2007.05.19 12:52:42 LOG7[264:4239]: connect_wait: waiting 10 seconds 2007.05.19 12:52:42 LOG7[264:4239]: connect_wait: connected 2007.05.19 12:52:42 LOG5[264:4239]: smtps connected remote server from 192.168.69.14:52673 2007.05.19 12:52:42 LOG7[264:4239]: Remote FD=15 initialized 2007.05.19 12:52:42 LOG7[264:4239]: TCP_NODELAY option set on remote socket 2007.05.19 12:52:42 LOG7[264:4239]: SSL state (connect): before/connect initialization 2007.05.19 12:52:42 LOG7[264:4239]: SSL state (connect): SSLv3 write client hello A 2007.05.19 12:52:42 LOG7[264:4239]: SSL alert (write): fatal: handshake failure 2007.05.19 12:52:42 LOG3[264:4239]: SSL_connect: 1408F10B: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number 2007.05.19 12:52:42 LOG5[264:4239]: Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket 2007.05.19 12:52:42 LOG7[264:4239]: smtps finished (0 left) - -- jimoe (at) sohnen-moe (dot) com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (OS/2) iD8DBQFGT1lQzTcr8Prq0ZMRAv50AJ9Kydmi3F/VBQ8hvpr+HmodUZhJEgCfQjbz TRdvnzpATUH/y3gzA1EXMYo= =jTqm -----END PGP SIGNATURE-----

1 0

Several connections on a short period of time problem
by Teigao, Rafael Coninck 16 May '07

16 May '07

Hi, I'm running Stunnel 4.20 to connect a Win client to a Win server. On the server it runs as a service, but on the client side I call it every time a connection is requested with a different config file (I need dynamic configuration) If I connect, disconnect and connect again very quickly (say, in 10 seconds), the fourth time (usually) that I try to connect will give me error 10060 (timeout) on the client application (not Stunnel). Does Stunnel restrict the amount of connection from the same client based on time or something like that? Thanks, Rafael.

1 0