- stunnel-users - stunnel.org

Outlook and stunnel
by James Devine 05 Jun '12

05 Jun '12

I am trying to setup stunnel to ssl proxy mail to an smtp server and this seems to work fine for thunderbird but when I try using outlook 2010 to connect via ssl I get the error: Send test e-mail message: Your server does not support the connection encryption type you have specified. Try changing the encryption method. For sslVersion I have the option of SSLv3 and TLSv1, all and SSLv2 do not seem to work so I'm not sure if that is the problem Anyone else run in to this or know what I might do to resolve it?

1 1

stunnel 4.53 released
by Michal Trojnara 03 Jun '12

03 Jun '12

Dear Users, I have released version 4.53 of stunnel. This is major a bugfix release. Upgrade is highly recommended. The ChangeLog entry: Version 4.53, 2012.03.19, urgency: MEDIUM: * New features - Added client-mode "sni" option to directly control the value of TLS Server Name Indication (RFC 3546) extension. - Added support for IP_FREEBIND socket option with a pached Linux kernel. - Glibc-specific dynamic allocation tuning was applied to help unused memory deallocation. - Non-blocking OCSP implementation. * Bugfixes - Compilation fixes for old versions of OpenSSL (tested against 0.9.6). - Usage of uninitialized variables fixed in exec+connect services. - Occasional logging subsystem crash with exec+connect services. - OpenBSD compilation fix (thx to Michele Orru'). - Session id context initialized with session name rather than a constant. - Fixed handling of a rare inetd mode use case, where either stdin or stdout is a socket, but not both of them at the same time. - Fixed missing OPENSSL_Applink http://www.openssl.org/support/faq.html#PROG2 - Fixed crash on termination with FORK threading model. - Fixed dead canary after configuration reload with open connections. - Fixed missing file descriptors passed to local mode processes. - Fixed required jmp_buf alignment on Itanium platform. - Removed creating /dev/zero in the chroot jail on Solaris platform. - Fixed detection of WSAECONNREFUSED Winsock error. - Missing Microsoft.VC90.CRT.manifest added to Windows installer. Home page: http://www.stunnel.org/ Download: ftp://ftp.stunnel.org/stunnel/ SHA-256 hash for stunnel-4.53.tar.gz: 3e640aa4c96861d10addba758b66e99e7c5aec8697764f2a59ca2268901b8e57 Best regards, Mike

3 2

Re: [stunnel-users] BEAST Attack
by Scott McKeown 31 May '12

31 May '12

Hi Mike, Thank you for your input. I'll rebuild today and retest. Our company openly supports Open Source projects that we use and we will continue to do so. However, since we are still in a R&D position with STunnel at the moment I thought it would be better to continue to use the users group. I'll post again once I've rebuilt and tested, which might not be until the end of next week now as we have an nice extended weekend in the UK for the Golden Jubilee which is nice. ~Yours, Scott -- With Kind Regards. Scott McKeown Loadbalancer.org http://www.loadbalancer.org

1 0

Re: [stunnel-users] BEAST Attack
by Scott McKeown 30 May '12

30 May '12

Hi Michal, Thanks for following this up. I'm using the latest build of STunnel v4.53 as shown below (I check the site once a week just to make sure too) # stunnel -version stunnel 4.53 on x86_64-unknown-linux-gnu platform Compiled/running with OpenSSL 1.0.0-fips 29 Mar 2010 Threading:PTHREAD SSL:+ENGINE+OCSP+FIPS Auth:none Sockets:POLL+IPv6 Global options: debug = daemon.notice pid = /usr/local/var/run/stunnel/stunnel.pid RNDbytes = 64 RNDfile = /dev/urandom RNDoverwrite = yes Service-level options: ciphers = FIPS (with "fips = yes") ciphers = ALL:!SSLv2:!aNULL:!EXP:!LOW:-MEDIUM:RC4:+HIGH (with "fips = no") session = 300 seconds sslVersion = TLSv1 (with "fips = yes") sslVersion = TLSv1 for client, all for server (with "fips = no") stack = 65536 bytes TIMEOUTbusy = 300 seconds TIMEOUTclose = 60 seconds TIMEOUTconnect = 10 seconds TIMEOUTidle = 43200 seconds verify = none I've also included a copy of my stunnel.cfg file below: # more /etc/stunnel/stunnel.cfg # STunnel configuration file generated by loadbalancer.org appliance setgid = nobody pid = /stunnel.pid debug = 0 [S1] accept = 192.168.82.182:443 connect = 192.168.82.181:81 cert = /etc/loadbalancer.org/certs/S1.pem ciphers = RC4:HIGH:!MD5:!aNULL options = NO_SSLv2 protocol = proxy I'm looking to include the STunnel Product within our Loadbalancer Appliance in our next upcoming release but with everyone now using the SSL checker that I mentioned in one of my last e-Mails more customers are becoming concerned about MITM Attacks etc. so I would really like to get this solved before I move forward with the project. Oh, I guess I should also mention that this is running on a Centos 6.2 box. ~Yours, Scott

2 1

BEAST Attack
by Scott McKeown 29 May '12

29 May '12

Hi All, Has anyone looked at the current issue with the BEAST Attack. I'm looking at https://www.ssllabs.com/ssltest/index.html which can be used for testing SSL Certificates I also use Pound Proxy which I have now patched and this has removed the threat. However, I don't seem to be able to get the same result from a STunnel installation. If anyone can give some advice that would be great. ~Yours, Scott

3 5

limit to number of services
by Terren Suydam 25 May '12

25 May '12

Hi there, I seem to be hitting a limit on the number of stunnel services I can run simultaneously. According to the log, they appear to set up without any issues, but after 64 services they don't pass traffic. Is this something stunnel itself limits, or is it an OS limitation? I am running the latest windows build on Windows Server 2008. Either way, is there an easy way to increase the number of services? Thanks, Terren

1 0

Stunnel quitted unexpectedly repeated for a number of times
by Im Q 24 May '12

24 May '12

Hi all, We have encountered a strange situation that stunnel We have the following setup in our production servers. > Windows [ ... -> Apache -> Stunnel 4.50 ] --> AIX [Stunnel 4.50 -> JBoss] * As we had experienced the Stunnel in AIX died in a random time during testing stage, we added a cron job to start Stunnel in case stunnel disappeared. Recently, in our production servers, the stunnel disappeared and being started by corn repeatedly during a short period of time in the same day. We so far encounter similar problem for 2 times. Below are the restart time of the most recent incident. > 09:22:00,09:38:00,09:45:00, > 10:24:00,10:34:00,10:50:00, > 11:06:00,11:16:01,11:17:00,11:19:00,11:22:00,11:23:00,11:29:01,11:32:00,11:34:01,11:35:00,11:39:01 We found that in the logs, they always ended with the following: > 2012.05.23 11:16:03 LOG7[12517524:1]: Dispatching signals from the signal pipe > ... > 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD > ...(same message repeatly for serveral time) > 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD Here is the active options in config file: [Windows Side] > debug = 7 > output = D:\app-logs\stunnel\stunnel.log > verify = 0 > options = NO_SSLv2 > client = yes > taskbar = no > [prdweb01_out_app01] > accept = PRDWEB01:18009 > connect = PRDAPP01:18010 > [prdweb01_out_app02] > accept = PRDWEB01:18019 > connect = PRDAPP02:18010 [AIX Side] > pid = /opt/stunnel/4.50/prd/stunnel0-app/stunnel.pid > debug = 7 > output = /opt/stunnel/4.50/prd/stunnel0-app/log/stunnel.log > cert = /opt/stunnel/4.50/prd/stunnel0-app/PRD.certnew-b64.cer > key = /opt/stunnel/4.50/prd/stunnel0-app/PRD.private.key > options = NO_SSLv2 > [prdweb_in] > accept = PRDAPP01:18010 > connect = PRDAPP01:8009 Start up command > nohup stunnel /opt/stunnel/4.50/prd/stunnel0-app/stunnel-server.conf Attached at the end is the one of the log during the incident. Is there any suggestion on how to find out the cause of the problem? What are the possible causes that would make it disappeared after those processing of SIGCHLD signal? What may caused the signal dispatching other than killing them manually for shutdown? Thank you very much! Best Regards, Jacky -- LOG FILE CONTENT BELOW -- 2012.05.23 11:16:01 LOG7[11862064:1]: Clients allowed=31999 2012.05.23 11:16:01 LOG5[11862064:1]: stunnel 4.50 on powerpc-ibm-aix6.1.0.0 platform 2012.05.23 11:16:01 LOG5[11862064:1]: Compiled/running with OpenSSL 0.9.8m 25 Feb 2010 2012.05.23 11:16:01 LOG5[11862064:1]: Threading:PTHREAD SSL:ENGINE Auth:none Sockets:POLL,IPv6 2012.05.23 11:16:01 LOG5[11862064:1]: Reading configuration from file /opt/stunnel/4.50/prd/stunnel0-app/stunnel-server.conf 2012.05.23 11:16:01 LOG6[11862064:1]: Unable to retrieve any random data from /home/appadmin/.rnd 2012.05.23 11:16:01 LOG7[11862064:1]: Wrote 0 new random bytes to /home/appadmin/.rnd 2012.05.23 11:16:01 LOG7[11862064:1]: PRNG seeded successfully 2012.05.23 11:16:01 LOG6[11862064:1]: Initializing SSL context for service prdweb_in 2012.05.23 11:16:01 LOG4[11862064:1]: Insecure file permissions on /opt/stunnel/4.50/prd/stunnel0-app/PRD.private.key 2012.05.23 11:16:01 LOG7[11862064:1]: Certificate: /opt/stunnel/4.50/prd/stunnel0-app/PRD.certnew-b64.cer 2012.05.23 11:16:01 LOG7[11862064:1]: Certificate loaded 2012.05.23 11:16:01 LOG7[11862064:1]: Key file: /opt/stunnel/4.50/prd/stunnel0-app/PRD.private.key 2012.05.23 11:16:01 LOG7[11862064:1]: Private key loaded 2012.05.23 11:16:01 LOG7[11862064:1]: Could not load DH parameters from /opt/stunnel/4.50/prd/stunnel0-app/PRD.certnew-b64.cer 2012.05.23 11:16:01 LOG7[11862064:1]: Using hardcoded DH parameters 2012.05.23 11:16:01 LOG7[11862064:1]: DH initialized with 2048-bit key 2012.05.23 11:16:01 LOG7[11862064:1]: SSL options set: 0x01000004 2012.05.23 11:16:01 LOG6[11862064:1]: SSL context initialized 2012.05.23 11:16:01 LOG5[11862064:1]: Configuration successful 2012.05.23 11:16:01 LOG7[11862064:1]: Option SO_REUSEADDR set on accept socket 2012.05.23 11:16:01 LOG7[11862064:1]: Service prdweb_in bound to 10.18.7.71:18010 2012.05.23 11:16:01 LOG7[11862064:1]: Service prdweb_in opened FD=7 2012.05.23 11:16:01 LOG7[12517524:1]: Created pid file /opt/stunnel/4.50/prd/stunnel0-app/stunnel.pid 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=0 from 10.18.7.11:61657 2012.05.23 11:16:01 LOG7[12517524:258]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:258]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:258]: Service prdweb_in accepted connection from 10.18.7.11:61657 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=1 from 10.18.7.11:61685 2012.05.23 11:16:01 LOG7[12517524:515]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:515]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:515]: Service prdweb_in accepted connection from 10.18.7.11:61685 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=2 from 10.18.7.11:61667 2012.05.23 11:16:01 LOG7[12517524:772]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:772]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:772]: Service prdweb_in accepted connection from 10.18.7.11:61667 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=9 from 10.18.7.11:61659 2012.05.23 11:16:01 LOG7[12517524:1029]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:1029]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:1029]: Service prdweb_in accepted connection from 10.18.7.11:61659 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=10 from 10.18.7.12:64270 2012.05.23 11:16:01 LOG7[12517524:1286]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:1286]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:1286]: Service prdweb_in accepted connection from 10.18.7.12:64270 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=11 from 10.18.7.11:61669 2012.05.23 11:16:01 LOG7[12517524:1543]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:1543]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:1543]: Service prdweb_in accepted connection from 10.18.7.11:61669 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=12 from 10.18.7.12:64268 2012.05.23 11:16:01 LOG7[12517524:1800]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:1800]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:1800]: Service prdweb_in accepted connection from 10.18.7.12:64268 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=13 from 10.18.7.11:61671 2012.05.23 11:16:01 LOG7[12517524:2057]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:2057]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:2057]: Service prdweb_in accepted connection from 10.18.7.11:61671 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=14 from 10.18.7.11:61673 2012.05.23 11:16:01 LOG7[12517524:2314]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:2314]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:2314]: Service prdweb_in accepted connection from 10.18.7.11:61673 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=15 from 10.18.7.11:61677 2012.05.23 11:16:01 LOG7[12517524:2571]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:2571]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:2571]: Service prdweb_in accepted connection from 10.18.7.11:61677 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=16 from 10.18.7.11:61676 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=18 from 10.18.7.12:64272 2012.05.23 11:16:01 LOG7[12517524:3085]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:3085]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:3085]: Service prdweb_in accepted connection from 10.18.7.12:64272 2012.05.23 11:16:01 LOG7[12517524:2828]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:2828]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:2828]: Service prdweb_in accepted connection from 10.18.7.11:61676 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=17 from 10.18.7.11:61661 2012.05.23 11:16:01 LOG7[12517524:3342]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:3342]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:3342]: Service prdweb_in accepted connection from 10.18.7.11:61661 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=19 from 10.18.7.11:61687 2012.05.23 11:16:01 LOG7[12517524:3599]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:3599]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:3599]: Service prdweb_in accepted connection from 10.18.7.11:61687 2012.05.23 11:16:01 LOG6[12517524:1286]: SSL accepted: new session negotiated 2012.05.23 11:16:01 LOG6[12517524:1286]: Negotiated ciphers: DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1 2012.05.23 11:16:01 LOG6[12517524:1286]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:01 LOG5[12517524:1286]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:01 LOG5[12517524:1286]: Service prdweb_in connected remote server from 10.18.7.71:56505 2012.05.23 11:16:01 LOG7[12517524:1286]: Remote FD=20 initialized 2012.05.23 11:16:01 LOG7[12517524:1286]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=21 from 10.18.7.11:61663 2012.05.23 11:16:01 LOG7[12517524:3856]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:3856]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:3856]: Service prdweb_in accepted connection from 10.18.7.11:61663 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=22 from 10.18.7.11:61665 2012.05.23 11:16:01 LOG7[12517524:4113]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=23 from 10.18.7.12:64274 2012.05.23 11:16:01 LOG7[12517524:4370]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:4113]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG7[12517524:4370]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:4370]: Service prdweb_in accepted connection from 10.18.7.12:64274 2012.05.23 11:16:01 LOG5[12517524:4113]: Service prdweb_in accepted connection from 10.18.7.11:61665 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=24 from 10.18.7.11:61681 2012.05.23 11:16:01 LOG7[12517524:4627]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:4627]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:4627]: Service prdweb_in accepted connection from 10.18.7.11:61681 2012.05.23 11:16:01 LOG6[12517524:1800]: SSL accepted: new session negotiated 2012.05.23 11:16:01 LOG6[12517524:1800]: Negotiated ciphers: DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1 2012.05.23 11:16:01 LOG6[12517524:1800]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:01 LOG5[12517524:1800]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:01 LOG5[12517524:1800]: Service prdweb_in connected remote server from 10.18.7.71:35492 2012.05.23 11:16:01 LOG7[12517524:1800]: Remote FD=25 initialized 2012.05.23 11:16:01 LOG7[12517524:1800]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=26 from 10.18.7.11:61689 2012.05.23 11:16:01 LOG7[12517524:4884]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:4884]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:4884]: Service prdweb_in accepted connection from 10.18.7.11:61689 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=27 from 10.18.7.12:64276 2012.05.23 11:16:01 LOG7[12517524:5141]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:5141]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:5141]: Service prdweb_in accepted connection from 10.18.7.12:64276 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=28 from 10.18.7.12:64278 2012.05.23 11:16:01 LOG7[12517524:5398]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:5398]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:5398]: Service prdweb_in accepted connection from 10.18.7.12:64278 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=29 from 10.18.7.12:64280 2012.05.23 11:16:01 LOG7[12517524:5655]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:5655]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:5655]: Service prdweb_in accepted connection from 10.18.7.12:64280 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=30 from 10.18.7.11:61680 2012.05.23 11:16:01 LOG7[12517524:5912]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:5912]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:5912]: Service prdweb_in accepted connection from 10.18.7.11:61680 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=31 from 10.18.7.12:64282 2012.05.23 11:16:01 LOG7[12517524:6169]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:6169]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:6169]: Service prdweb_in accepted connection from 10.18.7.12:64282 2012.05.23 11:16:01 LOG6[12517524:3085]: SSL accepted: new session negotiated 2012.05.23 11:16:01 LOG6[12517524:3085]: Negotiated ciphers: DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1 2012.05.23 11:16:01 LOG6[12517524:3085]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:01 LOG5[12517524:3085]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:01 LOG5[12517524:3085]: Service prdweb_in connected remote server from 10.18.7.71:52373 2012.05.23 11:16:01 LOG7[12517524:3085]: Remote FD=32 initialized 2012.05.23 11:16:01 LOG7[12517524:3085]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=33 from 10.18.7.11:61683 2012.05.23 11:16:01 LOG7[12517524:6426]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:6426]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:6426]: Service prdweb_in accepted connection from 10.18.7.11:61683 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=34 from 10.18.7.12:64284 2012.05.23 11:16:01 LOG7[12517524:6683]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:6683]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:6683]: Service prdweb_in accepted connection from 10.18.7.12:64284 2012.05.23 11:16:01 LOG6[12517524:258]: SSL accepted: new session negotiated 2012.05.23 11:16:01 LOG6[12517524:258]: Negotiated ciphers: DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1 2012.05.23 11:16:01 LOG6[12517524:258]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:01 LOG5[12517524:258]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:01 LOG5[12517524:258]: Service prdweb_in connected remote server from 10.18.7.71:33167 2012.05.23 11:16:01 LOG7[12517524:258]: Remote FD=35 initialized 2012.05.23 11:16:01 LOG7[12517524:258]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:02 LOG6[12517524:4370]: SSL accepted: new session negotiated 2012.05.23 11:16:02 LOG6[12517524:4370]: Negotiated ciphers: DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1 2012.05.23 11:16:02 LOG6[12517524:4370]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:4370]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:4370]: Service prdweb_in connected remote server from 10.18.7.71:53609 2012.05.23 11:16:02 LOG7[12517524:4370]: Remote FD=36 initialized 2012.05.23 11:16:02 LOG7[12517524:4370]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:02 LOG6[12517524:5398]: SSL accepted: new session negotiated 2012.05.23 11:16:02 LOG6[12517524:5398]: Negotiated ciphers: DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1 2012.05.23 11:16:02 LOG6[12517524:5398]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:5398]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:5398]: Service prdweb_in connected remote server from 10.18.7.71:40822 2012.05.23 11:16:02 LOG7[12517524:5398]: Remote FD=37 initialized 2012.05.23 11:16:02 LOG7[12517524:5398]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:02 LOG7[12517524:1]: Service prdweb_in accepted FD=38 from 10.18.7.11:61691 2012.05.23 11:16:02 LOG7[12517524:6940]: Service prdweb_in started 2012.05.23 11:16:02 LOG7[12517524:6940]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:02 LOG5[12517524:6940]: Service prdweb_in accepted connection from 10.18.7.11:61691 2012.05.23 11:16:02 LOG6[12517524:5655]: SSL accepted: new session negotiated 2012.05.23 11:16:02 LOG6[12517524:5655]: Negotiated ciphers: DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1 2012.05.23 11:16:02 LOG6[12517524:5655]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:5655]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:5655]: Service prdweb_in connected remote server from 10.18.7.71:53430 2012.05.23 11:16:02 LOG7[12517524:5655]: Remote FD=39 initialized 2012.05.23 11:16:02 LOG7[12517524:5655]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:02 LOG7[12517524:1]: Service prdweb_in accepted FD=40 from 10.18.7.12:64286 2012.05.23 11:16:02 LOG7[12517524:7197]: Service prdweb_in started 2012.05.23 11:16:02 LOG7[12517524:7197]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:02 LOG5[12517524:7197]: Service prdweb_in accepted connection from 10.18.7.12:64286 2012.05.23 11:16:02 LOG7[12517524:5655]: SSL closed on SSL_read 2012.05.23 11:16:02 LOG7[12517524:5655]: Sending socket write shutdown 2012.05.23 11:16:02 LOG7[12517524:1]: Service prdweb_in accepted FD=41 from 10.18.7.11:61693 2012.05.23 11:16:02 LOG7[12517524:7454]: Service prdweb_in started 2012.05.23 11:16:02 LOG7[12517524:7454]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:02 LOG5[12517524:7454]: Service prdweb_in accepted connection from 10.18.7.11:61693 2012.05.23 11:16:02 LOG7[12517524:1]: Service prdweb_in accepted FD=42 from 10.18.7.11:61695 2012.05.23 11:16:02 LOG7[12517524:7711]: Service prdweb_in started 2012.05.23 11:16:02 LOG7[12517524:7711]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:02 LOG5[12517524:7711]: Service prdweb_in accepted connection from 10.18.7.11:61695 2012.05.23 11:16:02 LOG6[12517524:515]: SSL accepted: new session negotiated 2012.05.23 11:16:02 LOG6[12517524:515]: Negotiated ciphers: DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1 2012.05.23 11:16:02 LOG6[12517524:515]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:515]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:515]: Service prdweb_in connected remote server from 10.18.7.71:50558 2012.05.23 11:16:02 LOG7[12517524:515]: Remote FD=43 initialized 2012.05.23 11:16:02 LOG7[12517524:515]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:02 LOG6[12517524:1029]: SSL accepted: new session negotiated 2012.05.23 11:16:02 LOG6[12517524:1029]: Negotiated ciphers: DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1 2012.05.23 11:16:02 LOG6[12517524:1029]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:1029]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:1029]: Service prdweb_in connected remote server from 10.18.7.71:57414 2012.05.23 11:16:02 LOG7[12517524:1029]: Remote FD=44 initialized 2012.05.23 11:16:02 LOG7[12517524:1029]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:02 LOG7[12517524:1]: Service prdweb_in accepted FD=45 from 10.18.7.12:64288 2012.05.23 11:16:02 LOG7[12517524:7968]: Service prdweb_in started 2012.05.23 11:16:02 LOG7[12517524:7968]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:02 LOG5[12517524:7968]: Service prdweb_in accepted connection from 10.18.7.12:64288 2012.05.23 11:16:02 LOG7[12517524:1]: Service prdweb_in accepted FD=46 from 10.18.7.12:64290 2012.05.23 11:16:02 LOG7[12517524:8225]: Service prdweb_in started 2012.05.23 11:16:02 LOG7[12517524:8225]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:02 LOG5[12517524:8225]: Service prdweb_in accepted connection from 10.18.7.12:64290 2012.05.23 11:16:02 LOG6[12517524:772]: SSL accepted: new session negotiated 2012.05.23 11:16:02 LOG6[12517524:772]: Negotiated ciphers: DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1 2012.05.23 11:16:02 LOG6[12517524:772]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:772]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:772]: Service prdweb_in connected remote server from 10.18.7.71:33957 2012.05.23 11:16:02 LOG7[12517524:772]: Remote FD=47 initialized 2012.05.23 11:16:02 LOG7[12517524:772]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:02 LOG6[12517524:8225]: SSL accepted: previous session reused 2012.05.23 11:16:02 LOG6[12517524:8225]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:8225]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:02 LOG6[12517524:7968]: SSL accepted: previous session reused 2012.05.23 11:16:02 LOG5[12517524:8225]: Service prdweb_in connected remote server from 10.18.7.71:36648 2012.05.23 11:16:02 LOG6[12517524:7968]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:02 LOG7[12517524:8225]: Remote FD=48 initialized 2012.05.23 11:16:02 LOG7[12517524:8225]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:02 LOG5[12517524:7968]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:7968]: Service prdweb_in connected remote server from 10.18.7.71:38529 2012.05.23 11:16:02 LOG7[12517524:7968]: Remote FD=49 initialized 2012.05.23 11:16:02 LOG7[12517524:7968]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:02 LOG7[12517524:1]: Service prdweb_in accepted FD=50 from 10.18.7.11:61697 2012.05.23 11:16:02 LOG7[12517524:8482]: Service prdweb_in started 2012.05.23 11:16:02 LOG7[12517524:8482]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:02 LOG5[12517524:8482]: Service prdweb_in accepted connection from 10.18.7.11:61697 2012.05.23 11:16:02 LOG6[12517524:3599]: SSL accepted: new session negotiated 2012.05.23 11:16:02 LOG6[12517524:3599]: Negotiated ciphers: DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1 2012.05.23 11:16:02 LOG6[12517524:3599]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:3599]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:3599]: Service prdweb_in connected remote server from 10.18.7.71:65426 2012.05.23 11:16:02 LOG7[12517524:3599]: Remote FD=51 initialized 2012.05.23 11:16:02 LOG7[12517524:3599]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:02 LOG6[12517524:3856]: SSL accepted: new session negotiated 2012.05.23 11:16:02 LOG6[12517524:3856]: Negotiated ciphers: DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1 2012.05.23 11:16:02 LOG6[12517524:3856]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:3856]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:3856]: Service prdweb_in connected remote server from 10.18.7.71:51278 2012.05.23 11:16:02 LOG7[12517524:3856]: Remote FD=52 initialized 2012.05.23 11:16:02 LOG7[12517524:3856]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:02 LOG7[12517524:3856]: SSL closed on SSL_read 2012.05.23 11:16:02 LOG7[12517524:3856]: Sending socket write shutdown 2012.05.23 11:16:02 LOG7[12517524:4370]: SSL closed on SSL_read 2012.05.23 11:16:02 LOG7[12517524:4370]: Sending socket write shutdown 2012.05.23 11:16:02 LOG7[12517524:1]: Service prdweb_in accepted FD=53 from 10.18.7.11:61699 2012.05.23 11:16:02 LOG7[12517524:8739]: Service prdweb_in started 2012.05.23 11:16:02 LOG7[12517524:8739]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:02 LOG5[12517524:8739]: Service prdweb_in accepted connection from 10.18.7.11:61699 2012.05.23 11:16:02 LOG6[12517524:4113]: SSL accepted: new session negotiated 2012.05.23 11:16:02 LOG6[12517524:4113]: Negotiated ciphers: DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1 2012.05.23 11:16:02 LOG6[12517524:4113]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:4113]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:4113]: Service prdweb_in connected remote server from 10.18.7.71:33279 2012.05.23 11:16:02 LOG7[12517524:4113]: Remote FD=54 initialized 2012.05.23 11:16:02 LOG7[12517524:4113]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:02 LOG6[12517524:8482]: SSL accepted: previous session reused 2012.05.23 11:16:02 LOG7[12517524:4113]: SSL closed on SSL_read 2012.05.23 11:16:02 LOG7[12517524:4113]: Sending socket write shutdown 2012.05.23 11:16:02 LOG6[12517524:8482]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:8482]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:8482]: Service prdweb_in connected remote server from 10.18.7.71:50727 2012.05.23 11:16:02 LOG7[12517524:8482]: Remote FD=55 initialized 2012.05.23 11:16:02 LOG7[12517524:8482]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:02 LOG7[12517524:1]: Service prdweb_in accepted FD=56 from 10.18.7.11:61701 2012.05.23 11:16:02 LOG7[12517524:8996]: Service prdweb_in started 2012.05.23 11:16:02 LOG7[12517524:8996]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:02 LOG5[12517524:8996]: Service prdweb_in accepted connection from 10.18.7.11:61701 2012.05.23 11:16:02 LOG7[12517524:1]: Service prdweb_in accepted FD=57 from 10.18.7.11:61703 2012.05.23 11:16:02 LOG7[12517524:9253]: Service prdweb_in started 2012.05.23 11:16:02 LOG7[12517524:9253]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:02 LOG5[12517524:9253]: Service prdweb_in accepted connection from 10.18.7.11:61703 2012.05.23 11:16:02 LOG7[12517524:1]: Service prdweb_in accepted FD=58 from 10.18.7.11:61705 2012.05.23 11:16:02 LOG7[12517524:1]: Service prdweb_in accepted FD=59 from 10.18.7.11:61707 2012.05.23 11:16:02 LOG7[12517524:9510]: Service prdweb_in started 2012.05.23 11:16:02 LOG7[12517524:9510]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:02 LOG5[12517524:9510]: Service prdweb_in accepted connection from 10.18.7.11:61705 2012.05.23 11:16:02 LOG7[12517524:9767]: Service prdweb_in started 2012.05.23 11:16:02 LOG7[12517524:9767]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:02 LOG5[12517524:9767]: Service prdweb_in accepted connection from 10.18.7.11:61707 2012.05.23 11:16:02 LOG7[12517524:1]: Service prdweb_in accepted FD=60 from 10.18.7.11:61709 2012.05.23 11:16:02 LOG7[12517524:10024]: Service prdweb_in started 2012.05.23 11:16:02 LOG7[12517524:10024]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:02 LOG5[12517524:10024]: Service prdweb_in accepted connection from 10.18.7.11:61709 2012.05.23 11:16:02 LOG7[12517524:1]: Service prdweb_in accepted FD=61 from 10.18.7.12:64292 2012.05.23 11:16:02 LOG7[12517524:10281]: Service prdweb_in started 2012.05.23 11:16:02 LOG7[12517524:10281]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:02 LOG5[12517524:10281]: Service prdweb_in accepted connection from 10.18.7.12:64292 2012.05.23 11:16:03 LOG6[12517524:5912]: SSL accepted: new session negotiated 2012.05.23 11:16:03 LOG6[12517524:5912]: Negotiated ciphers: DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1 2012.05.23 11:16:03 LOG6[12517524:5912]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:5912]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:5912]: Service prdweb_in connected remote server from 10.18.7.71:59860 2012.05.23 11:16:03 LOG7[12517524:5912]: Remote FD=62 initialized 2012.05.23 11:16:03 LOG7[12517524:5912]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:03 LOG6[12517524:8739]: SSL accepted: previous session reused 2012.05.23 11:16:03 LOG6[12517524:8739]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:8739]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:8739]: Service prdweb_in connected remote server from 10.18.7.71:33186 2012.05.23 11:16:03 LOG7[12517524:8739]: Remote FD=63 initialized 2012.05.23 11:16:03 LOG7[12517524:8739]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:03 LOG6[12517524:8996]: SSL accepted: previous session reused 2012.05.23 11:16:03 LOG6[12517524:8996]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:8996]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:8996]: Service prdweb_in connected remote server from 10.18.7.71:46952 2012.05.23 11:16:03 LOG7[12517524:8996]: Remote FD=64 initialized 2012.05.23 11:16:03 LOG7[12517524:8996]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:03 LOG6[12517524:9510]: SSL accepted: previous session reused 2012.05.23 11:16:03 LOG6[12517524:9510]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:9510]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:9510]: Service prdweb_in connected remote server from 10.18.7.71:48237 2012.05.23 11:16:03 LOG7[12517524:9510]: Remote FD=65 initialized 2012.05.23 11:16:03 LOG7[12517524:9510]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:03 LOG6[12517524:9253]: SSL accepted: previous session reused 2012.05.23 11:16:03 LOG6[12517524:9253]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:9253]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:9253]: Service prdweb_in connected remote server from 10.18.7.71:54984 2012.05.23 11:16:03 LOG7[12517524:9253]: Remote FD=66 initialized 2012.05.23 11:16:03 LOG7[12517524:9253]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:03 LOG6[12517524:9767]: SSL accepted: previous session reused 2012.05.23 11:16:03 LOG6[12517524:9767]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:9767]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:9767]: Service prdweb_in connected remote server from 10.18.7.71:33305 2012.05.23 11:16:03 LOG7[12517524:9767]: Remote FD=67 initialized 2012.05.23 11:16:03 LOG7[12517524:9767]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:03 LOG6[12517524:10024]: SSL accepted: previous session reused 2012.05.23 11:16:03 LOG6[12517524:10024]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:10024]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:10024]: Service prdweb_in connected remote server from 10.18.7.71:48123 2012.05.23 11:16:03 LOG6[12517524:7197]: SSL accepted: previous session reused 2012.05.23 11:16:03 LOG6[12517524:7197]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:7197]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:7197]: Service prdweb_in connected remote server from 10.18.7.71:38228 2012.05.23 11:16:03 LOG7[12517524:7197]: Remote FD=69 initialized 2012.05.23 11:16:03 LOG7[12517524:7197]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:03 LOG6[12517524:6683]: SSL accepted: previous session reused 2012.05.23 11:16:03 LOG6[12517524:6683]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:6683]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:6683]: Service prdweb_in connected remote server from 10.18.7.71:51522 2012.05.23 11:16:03 LOG7[12517524:6683]: Remote FD=70 initialized 2012.05.23 11:16:03 LOG7[12517524:6683]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:03 LOG6[12517524:10281]: SSL accepted: previous session reused 2012.05.23 11:16:03 LOG6[12517524:10281]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:10281]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:10281]: Service prdweb_in connected remote server from 10.18.7.71:51109 2012.05.23 11:16:03 LOG7[12517524:10281]: Remote FD=71 initialized 2012.05.23 11:16:03 LOG7[12517524:10281]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:03 LOG7[12517524:10024]: Remote FD=68 initialized 2012.05.23 11:16:03 LOG7[12517524:1]: Dispatching signals from the signal pipe 2012.05.23 11:16:03 LOG7[12517524:10024]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD

1 0

Re: [stunnel-users] Stunnel not working
by Ludolf Holzheid 21 May '12

21 May '12

On Mon, 2012-05-21 18:09:35 +1000, Peter Connor wrote: > > Hi > I tried to reload stunnel.conf but I received error message says "Stunnel server is down due to error. You need to exit and correct the problem. Click OK to see the error log window". So I looked in error log window, it says: > "Server is downReading configuration from file stunnel.confFIPS mode is enabledCompression not enabledSnagged 64 random bytes from C:/.rndWrote 1024 new random bytes to C:/.rndPRNG seeded successfullyLine 66: "connect secure.giganews.com:563": No '=' found > Server is down" > My operating system windows home XP. Any ideas how to fix this problem. Please help. Thanks > Peter Peter, I don't know why you are asking me and not the stunnel users list. Anyway, it seems to be what the error log says: Line 66 of your stunnel.conf is lacking an equal sign. HTH, Ludolf -- --------------------------------------------------------------- Ludolf Holzheid Tel: +49 621 339960 Bihl+Wiedemann GmbH Fax: +49 621 3392239 Floßwörthstraße 41 e-mail: lholzheid(a)bihl-wiedemann.de D-68199 Mannheim, Germany ---------------------------------------------------------------

1 0

First message flows through second one does not
by George Cardenas 19 May '12

19 May '12

I been chasing my tail a few days now reading through every post and searching in the internet how to work around this issue. The first message will flow though but any other messages after that wont. The log doesn't tell me anything besides that the first attempt sent more bytes than the second attempt. Can someone see anything else I might have overlooked? 2012.05.18 12:07:14 LOG7[2236:3940]: Service [SMTP Outgoing] accepted (FD=360) from 127.0.0.1:1638 2012.05.18 12:07:14 LOG7[2236:3940]: Creating a new thread 2012.05.18 12:07:14 LOG7[2236:3940]: New thread created 2012.05.18 12:07:14 LOG7[2236:580]: Service [SMTP Outgoing] started 2012.05.18 12:07:14 LOG5[2236:580]: Service [SMTP Outgoing] accepted connection from 127.0.0.1:1638 2012.05.18 12:07:14 LOG6[2236:580]: connect_blocking: connecting 157.56.234.134:587 2012.05.18 12:07:14 LOG7[2236:580]: connect_blocking: s_poll_wait 157.56.234.134:587: waiting 10 seconds 2012.05.18 12:07:14 LOG5[2236:580]: connect_blocking: connected 157.56.234.134:587 2012.05.18 12:07:14 LOG5[2236:580]: Service [SMTP Outgoing] connected remote server from 10.0.0.65:1639 2012.05.18 12:07:14 LOG7[2236:580]: Remote socket (FD=372) initialized 2012.05.18 12:07:14 LOG6[2236:580]: Client-mode smtp protocol negotiations started 2012.05.18 12:07:14 LOG7[2236:580]: <- 220 pod51011.outlook.com Microsoft ESMTP MAIL Service ready at Fri, 18 May 2012 16:07:13 +0000 2012.05.18 12:07:14 LOG7[2236:580]: -> 220 pod51011.outlook.com Microsoft ESMTP MAIL Service ready at Fri, 18 May 2012 16:07:13 +0000 2012.05.18 12:07:14 LOG7[2236:580]: -> EHLO localhost 2012.05.18 12:07:14 LOG7[2236:580]: <- 250-pod51011.outlook.com Hello [65.23.214.191] 2012.05.18 12:07:14 LOG7[2236:580]: <- 250-SIZE 36700160 2012.05.18 12:07:14 LOG7[2236:580]: <- 250-PIPELINING 2012.05.18 12:07:14 LOG7[2236:580]: <- 250-DSN 2012.05.18 12:07:14 LOG7[2236:580]: <- 250-ENHANCEDSTATUSCODES 2012.05.18 12:07:14 LOG7[2236:580]: <- 250-STARTTLS 2012.05.18 12:07:14 LOG7[2236:580]: <- 250-AUTH 2012.05.18 12:07:14 LOG7[2236:580]: <- 250-8BITMIME 2012.05.18 12:07:14 LOG7[2236:580]: <- 250-BINARYMIME 2012.05.18 12:07:14 LOG7[2236:580]: <- 250 CHUNKING 2012.05.18 12:07:14 LOG7[2236:580]: -> STARTTLS 2012.05.18 12:07:14 LOG7[2236:580]: <- 220 2.0.0 SMTP server ready 2012.05.18 12:07:14 LOG6[2236:580]: Client-mode smtp protocol negotiations succeeded 2012.05.18 12:07:15 LOG6[2236:580]: SSL connected: new session negotiated 2012.05.18 12:07:15 LOG6[2236:580]: Negotiated TLSv1/SSLv3 ciphersuite: AES128-SHA (128-bit encryption) 2012.05.18 12:07:15 LOG6[2236:580]: Compression: null, expansion: null 2012.05.18 12:07:18 LOG7[2236:580]: SSL socket closed on SSL_read 2012.05.18 12:07:18 LOG7[2236:580]: Sent socket write shutdown 2012.05.18 12:07:18 LOG5[2236:580]: Connection closed: 1498 byte(s) sent to SSL, 498 byte(s) sent to socket 2012.05.18 12:07:18 LOG7[2236:580]: Remote socket (FD=372) closed 2012.05.18 12:07:18 LOG7[2236:580]: Local socket (FD=360) closed 2012.05.18 12:07:18 LOG7[2236:580]: Service [SMTP Outgoing] finished (0 left) 2012.05.18 12:07:18 LOG7[2236:580]: str_stats: 12 block(s), 298 data byte(s), 504 control byte(s) 2012.05.18 12:08:05 LOG7[2236:3940]: Service [SMTP Outgoing] accepted (FD=336) from 127.0.0.1:1644 2012.05.18 12:08:05 LOG7[2236:3940]: Creating a new thread 2012.05.18 12:08:05 LOG7[2236:3940]: New thread created 2012.05.18 12:08:05 LOG7[2236:4044]: Service [SMTP Outgoing] started 2012.05.18 12:08:05 LOG5[2236:4044]: Service [SMTP Outgoing] accepted connection from 127.0.0.1:1644 2012.05.18 12:08:05 LOG6[2236:4044]: connect_blocking: connecting 157.56.236.118:587 2012.05.18 12:08:05 LOG7[2236:4044]: connect_blocking: s_poll_wait 157.56.236.118:587: waiting 10 seconds 2012.05.18 12:08:05 LOG5[2236:4044]: connect_blocking: connected 157.56.236.118:587 2012.05.18 12:08:05 LOG5[2236:4044]: Service [SMTP Outgoing] connected remote server from 10.0.0.65:1645 2012.05.18 12:08:05 LOG7[2236:4044]: Remote socket (FD=376) initialized 2012.05.18 12:08:05 LOG6[2236:4044]: Client-mode smtp protocol negotiations started 2012.05.18 12:08:05 LOG7[2236:4044]: <- 220 pod51011.outlook.com Microsoft ESMTP MAIL Service ready at Fri, 18 May 2012 16:08:04 +0000 2012.05.18 12:08:05 LOG7[2236:4044]: -> 220 pod51011.outlook.com Microsoft ESMTP MAIL Service ready at Fri, 18 May 2012 16:08:04 +0000 2012.05.18 12:08:05 LOG7[2236:4044]: -> EHLO localhost 2012.05.18 12:08:05 LOG7[2236:4044]: <- 250-pod51011.outlook.com Hello [65.23.214.191] 2012.05.18 12:08:05 LOG7[2236:4044]: <- 250-SIZE 36700160 2012.05.18 12:08:05 LOG7[2236:4044]: <- 250-PIPELINING 2012.05.18 12:08:05 LOG7[2236:4044]: <- 250-DSN 2012.05.18 12:08:05 LOG7[2236:4044]: <- 250-ENHANCEDSTATUSCODES 2012.05.18 12:08:05 LOG7[2236:4044]: <- 250-STARTTLS 2012.05.18 12:08:05 LOG7[2236:4044]: <- 250-AUTH 2012.05.18 12:08:05 LOG7[2236:4044]: <- 250-8BITMIME 2012.05.18 12:08:05 LOG7[2236:4044]: <- 250-BINARYMIME 2012.05.18 12:08:05 LOG7[2236:4044]: <- 250 CHUNKING 2012.05.18 12:08:05 LOG7[2236:4044]: -> STARTTLS 2012.05.18 12:08:06 LOG7[2236:4044]: <- 220 2.0.0 SMTP server ready 2012.05.18 12:08:06 LOG6[2236:4044]: Client-mode smtp protocol negotiations succeeded 2012.05.18 12:08:06 LOG6[2236:4044]: SSL connected: new session negotiated 2012.05.18 12:08:06 LOG6[2236:4044]: Negotiated TLSv1/SSLv3 ciphersuite: AES128-SHA (128-bit encryption) 2012.05.18 12:08:06 LOG6[2236:4044]: Compression: null, expansion: null 2012.05.18 12:08:06 LOG7[2236:4044]: SSL socket closed on SSL_read 2012.05.18 12:08:06 LOG7[2236:4044]: Sent socket write shutdown 2012.05.18 12:08:06 LOG5[2236:4044]: Connection closed: 6 byte(s) sent to SSL, 48 byte(s) sent to socket 2012.05.18 12:08:06 LOG7[2236:4044]: Remote socket (FD=376) closed 2012.05.18 12:08:06 LOG7[2236:4044]: Local socket (FD=336) closed 2012.05.18 12:08:06 LOG7[2236:4044]: Service [SMTP Outgoing] finished (0 left) 2012.05.18 12:08:06 LOG7[2236:4044]: str_stats: 12 block(s), 298 data byte(s), 504 control byte(s)

2 1

Problem With GMail
by Van Brown 09 May '12

09 May '12

I am trying to use stunnel to act as a forwarder to GMail. My config file looks like:client = yes socket = l:TCP_NODELAY=1 socket = r:TCP_NODELAY=1 [gmail] accept = 25 connect = smtp.gmail.com:465 ;CAfile = peer-gmail.pem ;verify = 3 I saved the peer certificate and when I attempt to send mail, the log looks like this: 2012.05.08 16:01:35 LOG5[31036:19408]: Service [gmail] connected remote server from 192.168.1.9:42580 2012.05.08 16:01:35 LOG4[31036:19408]: CERT: Verification error: unable to get local issuer certificate 2012.05.08 16:01:35 LOG4[31036:19408]: Certificate check failed: depth=1, /C=US/O=Google Inc/CN=Google Internet Authority 2012.05.08 16:01:35 LOG3[31036:19408]: SSL_connect: 14090086: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed 2012.05.08 16:01:35 LOG5[31036:19408]: Connection reset: 0 byte(s) sent to SSL, 0 byte(s) sent to socket 2012.05.08 16:02:35 LOG5[31036:34312]: Service [gmail] accepted connection from 192.168.1.10:49303 2012.05.08 16:02:35 LOG5[31036:34312]: connect_blocking: connected 173.194.79.108:465 2012.05.08 16:02:35 LOG5[31036:34312]: Service [gmail] connected remote server from 192.168.1.9:42619 2012.05.08 16:02:36 LOG4[31036:34312]: CERT: Verification error: unable to get local issuer certificate 2012.05.08 16:02:36 LOG4[31036:34312]: Certificate check failed: depth=1, /C=US/O=Google Inc/CN=Google Internet Authority 2012.05.08 16:02:36 LOG3[31036:34312]: SSL_connect: 14090086: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed 2012.05.08 16:02:36 LOG5[31036:34312]: Connection reset: 0 byte(s) sent to SSL, 0 byte(s) sent to socket Please tell me what I'm doing wrong so I can fix it. Van Brown

2 1

Compiling stunnel without a cert
by Donovan Sydow 08 May '12

08 May '12

I'm trying to automate the compilation of stunnel from source and was curious if there was a hidden flag to prevent stunnel from trying to generate a certificate after running make install. I do know I can make a file called stunnel.pem in the system configuration directory prior to running make install to prevent the cert from being made, but ideally wanted a way to have stunnel install without having a cert pregenerated. I didn't see any configure flags to prevent this behavior. Does any one know how to bypass this requirement and compile without generating a certificate or having one already exist? Alternately I would be interested in hearing any suggestions on how to quietly generate the initial certificate as well in an automated (i.e. no input, quiet, etc.) fashion. Cheers, Donovan

1 0

Getting Stunnel to Work Under Windows 7 64-bit
by Thomas Eifert 03 May '12

03 May '12

For the benefit of the group, I thought I'd share some experiences I had when attempting to get Stunnel to run under Windows 7 SP1 64-bit. I initially installed Stunnel version 4.53 to the default location, which in Windows 7 64-bit is: C:\Program Files (x86)\stunnel\ I installed the service from the start menu option, then rebooted my machine. I have administrator rights, and User Account Control is disabled. My observations included the following: 1. The Stunnel status window displayed only configuration loads. No output from any active connection was ever displayed, despite the fact that Stunnel was passing traffic to/from SSL-enabled servers. 2. Stunnel would not write to the log file. The error message indicated that Stunnel was unable to open stunnel.log. Initially, I thought this might be a factor in the lack of status window connection output, so I commented the log statement out to eliminate it. I then reloaded the configuration. The issue of not seeing any connection info was unaffected. 3. The notification area icon would not appear on Stunnel service load. It would mysteriously appear, then disappear, at seemingly random times. 4. Once the service was installed, it was not possible to stop it or uninstall it from the provided start menu shortcuts. Whenever I attempted to do so, the Stunnel status window would appear. However, I was able to perform these actions successfully by opening a command prompt, then issuing the commands from there. In an effort to unravel these issues, I tried the following workarounds: 1. I re-installed stunnel to a non-system controlled directory. In my case, it was C:\Apps\stunnel\. 2. I attempted to run stunnel in compatibility mode, set for Windows XP SP3. 3. I tried installing 2 previous versions of Stunnel. All combinations produced exactly the same undesired result. Finally, I stopped and uninstalled the service. Instead of using that method, I created a shortcut to stunnel.exe, and placed it in the start menu's startup folder, then rebooted. Stunnel started at boot time, and all of the above issues were resolved. As such, it seems like Stunnel just doesn't like to be run as a service on a Windows 7 64-bit machine; at least not on the one I own. If you're encountering any stability issues with the Stunnel service in the Windows 7 64-bit environment, try my method. It works. I'd like to extend a special thank you to Carter Browne, who provided valuable input throughout the course of my testing. Regards, Thomas -- Attention: This message and all attachments are private and may contain information that is confidential and privileged. If you received this message in error, please notify the sender by reply email and delete the message immediately.

2 2

ssl3 handshake error
by Colin Chalmers 28 Apr '12

28 Apr '12

Hi all, I'm pretty new to stunnel but did get this config to work on a linux box - now I am trying the same/similiar config on a win7 box but keep getting the handshake error below. I am using the latest version of stunnel and have tried searching for an answer via google, making the proposed changes as described No matter what settings I use it always seems to use the sslv3 handshake which then goes wrong :-( I'd appreciate any help on this Colin My config is as follows: ; ************************************************************************** ; * Global options * ; ************************************************************************** ; Debugging stuff (may useful for troubleshooting) ; Some debugging stuff useful for troubleshooting debug = 7 output = c:\temp\stunnel.log ; Use it for client mode client = yes rndbytes = 256 rndfile = c:\temp\randseed.bin ; Some performance tunings socket = l:TCP_NODELAY=1 socket = r:TCP_NODELAY=1 ; Disable FIPS mode to allow non-approved protocols and algorithms fips = no ; ************************************************************************** ; * Service defaults may also be specified in individual service sections * ; ************************************************************************** ; Certificate/key is needed in server mode and optional in client mode cert = CT_20110324.pem ; Disable support for insecure SSLv2 protocol sslVersion = TLSv1 options = NO_SSLv2 options = NO_SSLv3 [CT] ; incoming connection from the client application accept = 444 ; outgoing connection connect = remote.server.com:443 TIMEOUTclose = 0 Error in log file 2012.04.11 18:33:54 LOG7[3684:3640]: Remote socket (FD=440) initialized 2012.04.11 18:33:54 LOG3[3684:3640]: SSL_connect: 14094410: error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure 2012.04.11 18:33:54 LOG5[3684:3640]: Connection reset: 0 byte(s) sent to SSL, 0 byte(s) sent to socket 2012.04.11 18:33:54 LOG7[3684:3640]: Remote socket (FD=440) closed 2012.04.11 18:33:54 LOG7[3684:3640]: Local socket (FD=408) closed 2012.04.11 18:33:54 LOG7[3684:3640]: Service [CT] finished (0 left)

3 2

Using Stunnel client but not Stunnel server with Apache mod_ssl
by Lilienberg, Daniel () 27 Apr '12

27 Apr '12

Hi, My supplier is using a somewhat strange setup looking like this: CLIENT: Stunnel running in client mode accepting incoming requests on port 8080. It will forward it to port to a server, port 443. SERVER: NOT running Stunnel at all, but running Apache with mod_ssl. It also acts as a proxy server, proxying all requests. Can this work, if so, how do I set it up ? [http://www.volvocars.net/support/IT/Services/IT_workplace/Email/outlook/sig…] Daniel Lilienberg Architect Connectivity Foundation Volvo Car Corporation Dept. 61630/PV2A Göteborg Sweden Telephone +46-31-3542317 dlilien2(a)volvocars.com<mailto:dlilien2@volvocars.com> www.volvocars.com<http://www.volvocars.com/> Registered Office Göteborg, Sweden Registration No. 556074-3089

1 0

Windows 7 64-Bit
by Thomas Eifert 23 Apr '12

23 Apr '12

Has anyone attempted to install and run Stunnel on Windows 7 64-bit? If so, which version did you use, and were any issues experienced? Regards. Thomas -- Attention: This message and all attachments are private and may contain information that is confidential and privileged. If you received this message in error, please notify the sender by reply email and delete the message immediately.

1 0

Possible error in stunnel 4.20
by Andreea Ion 20 Apr '12

20 Apr '12

Hi, I am running stunnel 4.2 on windows and I get the following log. I don't know if it's ok, if the problem is at the stunnel lovel or at the application level. SSL state (connect): before/connect initialization 2012.04.20 11:46:09 LOG7[5684:4492]: SSL state (connect): SSLv3 write client hello A 2012.04.20 11:46:09 LOG7[5684:4492]: SSL state (connect): SSLv3 read server hello A 2012.04.20 11:46:09 LOG7[5684:4492]: SSL state (connect): SSLv3 read finished A 2012.04.20 11:46:09 LOG7[5684:4492]: SSL state (connect): SSLv3 write change cipher spec A 2012.04.20 11:46:09 LOG7[5684:4492]: SSL state (connect): SSLv3 write finished A 2012.04.20 11:46:09 LOG7[5684:4492]: SSL state (connect): SSLv3 flush data 2012.04.20 11:46:09 LOG7[5684:4492]: 2 items in the session cache 2012.04.20 11:46:09 LOG7[5684:4492]: 5 client connects (SSL_connect()) 2012.04.20 11:46:09 LOG7[5684:4492]: 5 client connects that finished 2012.04.20 11:46:09 LOG7[5684:4492]: 0 client renegotiations requested 2012.04.20 11:46:09 LOG7[5684:4492]: 0 server connects (SSL_accept()) 2012.04.20 11:46:09 LOG7[5684:4492]: 0 server connects that finished 2012.04.20 11:46:09 LOG7[5684:4492]: 0 server renegotiations requested 2012.04.20 11:46:09 LOG7[5684:4492]: 3 session cache hits 2012.04.20 11:46:09 LOG7[5684:4492]: 0 session cache misses 2012.04.20 11:46:09 LOG7[5684:4492]: 0 session cache timeouts 2012.04.20 11:46:09 LOG6[5684:4492]: SSL connected: previous session reused 2012.04.20 11:46:54 LOG3[5684:4492]: readsocket: Connection reset by peer (WSAECONNRESET) (10054) 2012.04.20 11:46:54 LOG5[5684:4492]: Connection reset: 154 bytes sent to SSL, 0 bytes sent to socket 2012.04.20 11:46:54 LOG7[5684:4492]: Session finished (0 left) The last 3 lines are those that interests me most. Is this ok ? Regards, Andreea

1 0

(no subject)
by Guylhem 18 Apr '12

18 Apr '12

Hello With verify=3 and the certs loaded in the conf file with CAfile=startssl-chain.pem cert=mycert.pem, I get : CERT: Certificate not found in local repository Using the latest stunnel recompiled on a debian squeeze, the best I can get is: error queue: 140B0009: error:140B0009:SSL routines:SSL_CTX_use_PrivateKey_file:PEM lib SSL_CTX_use_PrivateKey_file: 906D06C: error:0906D06C:PEM routines:PEM_read_bio:no start line However, if I put these very same pem files in a directory as a CApath option instead (c_rehash applied) everything works fine. But The pem files are identical ! I've read http://stunnel.mirt.net/pipermail/stunnel-users/2010-November/002854.html but it seems a bit different The startssl-chain.pem was created with: wget http://www.startssl.com/certs/ca.pem wget http://www.startssl.com/certs/startssl.ca.pem cat sub.class1.server.ca.pem ca.pem > startssl-chain.pem I guess that may be the cause of the problem? What should I do to pass these pem files as stunnel.conf options instead of using the CApath? Guylhem

1 0

(no subject)
by Marco Tulio Jimenez Abrego 18 Apr '12

18 Apr '12

Buenos días El mensaje de error es: Error resolving 'smtp.gmail.com': Neither nodename nor servname known (EAI_NONAME). Gracias por su atención. -- Saludos. Att. Marco T. Jiménez ================ Tel. 6619-6782

3 2

Stunnel compiled with openssl 1.0.1 local binaries are 0.9.8k
by Michael Curran 11 Apr '12

11 Apr '12

Are there any potential known issues with stunnel being compiled using openssl 1.0.1 build and leaving the local system binaries at 0.9.8k Do you know of any way to test this for any incompatibilities? This was not my design, Im just being asked to support it and Im looking to make sure this method is not going to cause anything unusual.

2 1

PPID of child process
by Philip Wong 11 Apr '12

11 Apr '12

Hi, I’m trying to setup stunnel listening to multiple ports. The PPID of processes created are always root. Can we change that to the right PPID? Here I can see all the processes by killing 10764 and I expect this is the PPID. But all the children PPID are still 1; UID PID PPID C STIME TTY TIME CMD philwong 10759 1 0 16:27 pts/78 00:00:00 stunnel self.conf philwong 10760 1 0 16:27 pts/78 00:00:00 stunnel self.conf philwong 10761 1 0 16:27 pts/78 00:00:00 stunnel self.conf philwong 10762 1 0 16:27 pts/78 00:00:00 stunnel self.conf philwong 10763 1 0 16:27 pts/78 00:00:00 stunnel self.conf philwong 10764 1 0 16:27 ? 00:00:00 stunnel self.conf Regards, Philip

3 6

the connection had to be retried using SSL 3.0. This typically means that the server is using very old software and may have other security issues :(
by Thomas Manson 10 Apr '12

10 Apr '12

Hi, while I'm trying to get stunnel working for more than a few hours, I've also notice this warning in google chrome : the connection had to be retried using SSL 3.0. This typically means that > the server is using very old software and may have other security issues. [image: Inline image 1] gmail for example has AES_128_CBC for crypting, can we get that without much effort? What should be set to get rid of this warning ? I thought SSL v3 was the best (quickly pick acrross several example on the net) what is the best setting for this ? Thanks for your help, Thomas. My config : debug = 7 output = /var/log/stunnel4/extranet.service.com_stunnel.log setuid = stunnel4 setgid = stunnel4 pid = /var/run/stunnel4/extranet.service.com.pid socket = l:TCP_NODELAY=1 socket = r:TCP_NODELAY=1 [extranet.service.com] key = /etc/stunnel/sites/extranet.service.com/extranet.service.com.key cert = /etc/stunnel/sites/extranet.service.com/extranet.service.com.crt accept = 8.90.17.4:443 connect = 127.0.0.1:82 sslVersion = SSLv3 TIMEOUTclose = 0

3 4

[Stunnel Guru needed] stunnel running, but no longer serve connection after a while ("Dispatching signals from the signal pipe" in logs ==> all stops)
by Thomas Manson 09 Apr '12

09 Apr '12

Hi All, I'm really struggling to make stunnel working for more than a few hours. (and the client is yelling hard...) (I solved some other issue : logging per website and making more than one stunnel works) To put it in a nutshell : - stunnel is running and working correctly (I can reach the website in https correctly) - after some hours I get the following situation : - stunnel is still running on linux - trying to connect to a website result in the connection taking very long time and then fails : "*The connection to * extranet.serviceplus-hse.com <http://extranet.website.com>* was interrupted. Error 101 (net::ERR_CONNECTION_RESET): The connection was reset.*" (Chrome) Same symptoms on IE9, Firefox & Lynx (on the server that runs stunnel) (see logs below) - The following logs are the last one seen in the log file : - 2012.04.03 23:33:28 LOG5[24792:140152610346752]: Service extranet.serviceplus-hse.com connected remote server from 127.0.0.1:36256 - 2012.04.03 23:33:28 LOG7[24792:140152610346752]: Remote FD=1 initialized - 2012.04.03 23:33:28 LOG7[24792:140152610346752]: Option TCP_NODELAY set on remote socket - 2012.04.03 23:33:41 LOG7[24792:140152610346752]: Socket closed on read - 2012.04.03 23:33:41 LOG7[24792:140152610346752]: Sending SSL write shutdown - 2012.04.03 23:33:41 LOG7[24792:140152610346752]: SSL alert (write): warning: close notify - 2012.04.03 23:33:41 LOG6[24792:140152610346752]: SSL_shutdown successfully sent close_notify - 2012.04.03 23:33:41 LOG3[24792:140152610346752]: transfer: s_poll_wait: TIMEOUTclose exceeded: closing - 2012.04.03 23:33:41 LOG5[24792:140152610346752]: Connection closed: 186584 bytes sent to SSL, 3275 bytes sent to socket - 2012.04.03 23:33:41 LOG7[24792:140152610346752]: Service extranet.serviceplus-hse.com finished (0 left) - 2012.04.04 06:25:04 LOG7[24792:140152610629408]: *Dispatching signals from the signal pipe * stopping the firewall & fail2ban do not change anything. (the last line is logged by this function : *static void signal_pipe_empty(void) ) * the base stunnel.log has the same ending : - 2012.04.03 21:10:42 LOG7[24778:139641780209408]: Service https-123monsite.com permitted by libwrap from 212.162.10.34:3244 - 2012.04.03 21:10:42 LOG5[24778:139641780209408]: Service https-123monsite.com accepted connection from 212.162.10.34:3244 - 2012.04.03 21:10:42 LOG7[24778:139641780209408]: SSL state (accept): before/accept initialization - 2012.04.03 21:10:42 LOG3[24778:139641780209408]: SSL_accept: 1408F10B: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number - 2012.04.03 21:10:42 LOG5[24778:139641780209408]: Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket - 2012.04.03 21:10:42 LOG7[24778:139641780209408]: Service https-123monsite.com finished (0 left) - 2012.04.04 06:25:04 LOG7[24778:139641780213536]: Dispatching signals from the signal pipe - and at the same time (2012.04.04 06:25:04) all logs file stops : - root@ns0:/var/log/stunnel4# ll - total 128 - drwxr-xr-x 2 stunnel4 stunnel4 4096 2012-04-04 12:10 . - drwxr-xr-x 14 root root 4096 2012-04-04 06:25 .. - -rw-r----- 1 stunnel4 stunnel4 98084 2012-04-04 *06:25*extranet.serviceplus-hse.com_stunnel.log - -rw-r----- 1 stunnel4 stunnel4 4491 2012-04-04 06:25 mansonthomas.com_stunnel.log - -rw-r----- 1 stunnel4 stunnel4 0 2012-04-04 06:25 stunnel.log - -rw-r----- 1 stunnel4 stunnel4 11058 2012-04-04 06:25 stunnel.log.1 - I've seen some message about the same behavior but after an upgrade on freebsd and didn't find any solution... - Restarting stunnel restore the service immediately. below some information about my configuration... ask for more if needed. Thanks for any helps, Regards, Thomas. Distribution & Pachage info (x64 system) ###################################################################### root@ns0:/var/log/stunnel4# cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=11.10 DISTRIB_CODENAME=oneiric DISTRIB_DESCRIPTION="Ubuntu 11.10" root@ns0:/var/log/stunnel4# aptitude show stunnel4 Package: stunnel4 New: yes State: installed Automatically installed: no Version: 3:*4.35-2build1* ###################################################################### lynx try : ###################################################################### root@ns0:/var/log/stunnel4# lynx https://extranet.serviceplus-hse.com Looking up extranet.serviceplus-hse.com Making HTTPS connection to extranet.serviceplus-hse.com Retrying connection without TLS. Looking up extranet.serviceplus-hse.com Making HTTPS connection to extranet.serviceplus-hse.com Alert!: Unable to make secure connection to remote host. lynx: Can't access startfile https://extranet.serviceplus-hse.com/ ###################################################################### ps -edf : ###################################################################### 1 24773 24762 18168 ? -1 S 109 0:00 /usr/bin/stunnel4 /etc/stunnel/base.conf TERM=screen-bce PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin LANG=en_US.UTF-8 PWD=/ 1 24774 24762 18168 ? -1 S 109 0:00 /usr/bin/stunnel4 /etc/stunnel/base.conf TERM=screen-bce PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin LANG=en_US.UTF-8 PWD=/ 1 24775 24762 18168 ? -1 S 109 0:00 /usr/bin/stunnel4 /etc/stunnel/base.conf TERM=screen-bce PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin LANG=en_US.UTF-8 PWD=/ 1 24776 24762 18168 ? -1 S 109 0:00 /usr/bin/stunnel4 /etc/stunnel/base.conf TERM=screen-bce PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin LANG=en_US.UTF-8 PWD=/ 1 24777 24762 18168 ? -1 S 109 0:00 /usr/bin/stunnel4 /etc/stunnel/base.conf TERM=screen-bce PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin LANG=en_US.UTF-8 PWD=/ 1 24778 24778 24778 ? -1 Ss 109 0:00 /usr/bin/stunnel4 /etc/stunnel/base.conf TERM=screen-bce PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin LANG=en_US.UTF-8 PWD=/ 1 24787 24762 18168 ? -1 S 109 0:00 /usr/bin/stunnel4 /etc/stunnel/extranet.serviceplus-hse.com.conf TERM=screen-bce PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin LANG=en_US.UTF-8 P 1 24788 24762 18168 ? -1 S 109 0:00 /usr/bin/stunnel4 /etc/stunnel/extranet.serviceplus-hse.com.conf TERM=screen-bce PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin LANG=en_US.UTF-8 P 1 24789 24762 18168 ? -1 S 109 0:00 /usr/bin/stunnel4 /etc/stunnel/extranet.serviceplus-hse.com.conf TERM=screen-bce PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin LANG=en_US.UTF-8 P 1 24790 24762 18168 ? -1 S 109 0:00 /usr/bin/stunnel4 /etc/stunnel/extranet.serviceplus-hse.com.conf TERM=screen-bce PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin LANG=en_US.UTF-8 P 1 24791 24762 18168 ? -1 S 109 0:00 /usr/bin/stunnel4 /etc/stunnel/extranet.serviceplus-hse.com.conf TERM=screen-bce PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin LANG=en_US.UTF-8 P 1 24792 24792 24792 ? -1 Ss 109 0:00 /usr/bin/stunnel4 /etc/stunnel/extranet.serviceplus-hse.com.conf TERM=screen-bce PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin LANG=en_US.UTF-8 P 1 24801 24762 18168 ? -1 S 109 0:00 /usr/bin/stunnel4 /etc/stunnel/mansonthomas.com.conf TERM=screen-bce PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin LANG=en_US.UTF-8 PWD=/ 1 24802 24762 18168 ? -1 S 109 0:00 /usr/bin/stunnel4 /etc/stunnel/mansonthomas.com.conf TERM=screen-bce PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin LANG=en_US.UTF-8 PWD=/ 1 24803 24762 18168 ? -1 S 109 0:00 /usr/bin/stunnel4 /etc/stunnel/mansonthomas.com.conf TERM=screen-bce PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin LANG=en_US.UTF-8 PWD=/ 1 24804 24762 18168 ? -1 S 109 0:00 /usr/bin/stunnel4 /etc/stunnel/mansonthomas.com.conf TERM=screen-bce PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin LANG=en_US.UTF-8 PWD=/ 1 24805 24762 18168 ? -1 S 109 0:00 /usr/bin/stunnel4 /etc/stunnel/mansonthomas.com.conf TERM=screen-bce PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin LANG=en_US.UTF-8 PWD=/ 1 24806 24806 24806 ? -1 Ss 109 0:00 /usr/bin/stunnel4 /etc/stunnel/mansonthomas.com.conf TERM=screen-bce PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin LANG=en_US.UTF-8 PWD=/ ###################################################################### /etc/stunnel/base.conf ###################################################################### debug = 7 sslVersion = SSLv3 cert=/etc/stunnel/sites/123monsite.com/123monsite.com.crt key=/etc/stunnel/sites/123monsite.com/123monsite.com.key ; security enhancements for UNIX systems ; for chroot a copy of some devices and files is needed within the jail ;chroot = /var/lib/stunnel4/ setuid = stunnel4 setgid = stunnel4 ; PID is created inside the chroot jail pid = /var/run/stunnel4/stunnel4.pid socket = l:TCP_NODELAY=1 socket = r:TCP_NODELAY=1 output = /var/log/stunnel4/stunnel.log [https-123monsite.com] accept=88.190.17.222:443 connect=127.0.0.1:82 ###################################################################### /etc/stunnel/extranet.serviceplus-hse.com.conf ###################################################################### debug = 7 output = /var/log/stunnel4/extranet.serviceplus-hse.com_stunnel.log setuid = stunnel4 setgid = stunnel4 pid = /var/run/stunnel4/extranet.serviceplus-hse.com.pid socket = l:TCP_NODELAY=1 socket = r:TCP_NODELAY=1 [extranet.serviceplus-hse.com] key = /etc/stunnel/sites/ extranet.serviceplus-hse.com/extranet.serviceplus-hse.com.key cert = /etc/stunnel/sites/ extranet.serviceplus-hse.com/extranet.serviceplus-hse.com.crt accept = 88.190.217.54:443 connect = 127.0.0.1:82 sslVersion = SSLv3 TIMEOUTclose = 0 ###################################################################### Last logs : /var/log/stunnel4/extranet.serviceplus-hse.com_stunnel.log ###################################################################### 2012.04.03 23:02:47 LOG6[24792:140152610346752]: SSL accepted: previous session reused 2012.04.03 23:02:47 LOG7[24792:140152610346752]: remote socket: FD=1 allocated (non-blocking mode) 2012.04.03 23:02:47 LOG6[24792:140152610346752]: connect_blocking: connecting 127.0.0.1:82 2012.04.03 23:02:47 LOG7[24792:140152610346752]: connect_blocking: s_poll_wait 127.0.0.1:82: waiting 10 seconds 2012.04.03 23:02:47 LOG5[24792:140152610346752]: connect_blocking: connected 127.0.0.1:82 2012.04.03 23:02:47 LOG5[24792:140152610346752]: Service extranet.serviceplus-hse.com connected remote server from 127.0.0.1:60624 2012.04.03 23:02:47 LOG7[24792:140152610346752]: Remote FD=1 initialized 2012.04.03 23:02:47 LOG7[24792:140152610346752]: Option TCP_NODELAY set on remote socket 2012.04.03 23:02:58 LOG7[24792:140152610346752]: Socket closed on read 2012.04.03 23:02:58 LOG7[24792:140152610346752]: Sending SSL write shutdown 2012.04.03 23:02:58 LOG7[24792:140152610346752]: SSL alert (write): warning: close notify 2012.04.03 23:02:58 LOG6[24792:140152610346752]: SSL_shutdown successfully sent close_notify 2012.04.03 23:02:58 LOG3[24792:140152610346752]: transfer: s_poll_wait: TIMEOUTclose exceeded: closing 2012.04.03 23:02:58 LOG5[24792:140152610346752]: Connection closed: 167313 bytes sent to SSL, 1871 bytes sent to socket 2012.04.03 23:02:58 LOG7[24792:140152610346752]: Service extranet.serviceplus-hse.com finished (0 left) 2012.04.03 23:33:20 LOG7[24792:140152610629408]: local socket: FD=0 allocated (non-blocking mode) 2012.04.03 23:33:20 LOG7[24792:140152610629408]: Service extranet.serviceplus-hse.com accepted FD=0 from 82.224.128.241:52114 2012.04.03 23:33:20 LOG7[24792:140152610346752]: Service extranet.serviceplus-hse.com started 2012.04.03 23:33:20 LOG7[24792:140152610346752]: Option TCP_NODELAY set on local socket 2012.04.03 23:33:20 LOG7[24792:140152610346752]: Waiting for a libwrap process 2012.04.03 23:33:20 LOG7[24792:140152610346752]: Acquired libwrap process #0 2012.04.03 23:33:20 LOG7[24792:140152610346752]: Releasing libwrap process #0 2012.04.03 23:33:20 LOG7[24792:140152610346752]: Released libwrap process #0 2012.04.03 23:33:20 LOG7[24792:140152610346752]: Service extranet.serviceplus-hse.com permitted by libwrap from 82.224.128.241:52114 2012.04.03 23:33:20 LOG5[24792:140152610346752]: Service extranet.serviceplus-hse.com accepted connection from 82.224.128.241:52114 2012.04.03 23:33:20 LOG7[24792:140152610346752]: SSL state (accept): before/accept initialization 2012.04.03 23:33:20 LOG7[24792:140152610346752]: SSL state (accept): SSLv3 read client hello B 2012.04.03 23:33:20 LOG7[24792:140152610346752]: SSL state (accept): SSLv3 write server hello A 2012.04.03 23:33:20 LOG7[24792:140152610346752]: SSL state (accept): SSLv3 write certificate A 2012.04.03 23:33:20 LOG7[24792:140152610346752]: SSL state (accept): SSLv3 write key exchange A 2012.04.03 23:33:20 LOG7[24792:140152610346752]: SSL state (accept): SSLv3 write server done A 2012.04.03 23:33:20 LOG7[24792:140152610346752]: SSL state (accept): SSLv3 flush data 2012.04.03 23:33:20 LOG7[24792:140152610346752]: SSL state (accept): SSLv3 read client key exchange A 2012.04.03 23:33:20 LOG7[24792:140152610346752]: SSL state (accept): SSLv3 read finished A 2012.04.03 23:33:20 LOG7[24792:140152610346752]: SSL state (accept): SSLv3 write change cipher spec A 2012.04.03 23:33:20 LOG7[24792:140152610346752]: SSL state (accept): SSLv3 write finished A 2012.04.03 23:33:20 LOG7[24792:140152610346752]: SSL state (accept): SSLv3 flush data 2012.04.03 23:33:20 LOG7[24792:140152610346752]: 7 items in the session cache 2012.04.03 23:33:20 LOG7[24792:140152610346752]: 0 client connects (SSL_connect()) 2012.04.03 23:33:20 LOG7[24792:140152610346752]: 0 client connects that finished 2012.04.03 23:33:20 LOG7[24792:140152610346752]: 0 client renegotiations requested 2012.04.03 23:33:20 LOG7[24792:140152610346752]: 21 server connects (SSL_accept()) 2012.04.03 23:33:20 LOG7[24792:140152610346752]: 20 server connects that finished 2012.04.03 23:33:20 LOG7[24792:140152610346752]: 0 server renegotiations requested 2012.04.03 23:33:20 LOG7[24792:140152610346752]: 9 session cache hits 2012.04.03 23:33:20 LOG7[24792:140152610346752]: 0 external session cache hits 2012.04.03 23:33:20 LOG7[24792:140152610346752]: 7 session cache misses 2012.04.03 23:33:20 LOG7[24792:140152610346752]: 4 session cache timeouts 2012.04.03 23:33:20 LOG6[24792:140152610346752]: SSL accepted: new session negotiated 2012.04.03 23:33:20 LOG6[24792:140152610346752]: Negotiated ciphers: DHE-RSA-CAMELLIA256-SHA SSLv3 Kx=DH Au=RSA Enc=Camellia(256) Mac=SHA1 2012.04.03 23:33:20 LOG7[24792:140152610346752]: remote socket: FD=1 allocated (non-blocking mode) 2012.04.03 23:33:20 LOG6[24792:140152610346752]: connect_blocking: connecting 127.0.0.1:82 2012.04.03 23:33:20 LOG7[24792:140152610346752]: connect_blocking: s_poll_wait 127.0.0.1:82: waiting 10 seconds 2012.04.03 23:33:20 LOG5[24792:140152610346752]: connect_blocking: connected 127.0.0.1:82 2012.04.03 23:33:20 LOG5[24792:140152610346752]: Service extranet.serviceplus-hse.com connected remote server from 127.0.0.1:36240 2012.04.03 23:33:20 LOG7[24792:140152610346752]: Remote FD=1 initialized 2012.04.03 23:33:20 LOG7[24792:140152610346752]: Option TCP_NODELAY set on remote socket 2012.04.03 23:33:27 LOG7[24792:140152610346752]: Socket closed on read 2012.04.03 23:33:27 LOG7[24792:140152610346752]: Sending SSL write shutdown 2012.04.03 23:33:27 LOG7[24792:140152610346752]: SSL alert (write): warning: close notify 2012.04.03 23:33:27 LOG6[24792:140152610346752]: SSL_shutdown successfully sent close_notify 2012.04.03 23:33:27 LOG3[24792:140152610346752]: transfer: s_poll_wait: TIMEOUTclose exceeded: closing 2012.04.03 23:33:27 LOG5[24792:140152610346752]: Connection closed: 537 bytes sent to SSL, 620 bytes sent to socket 2012.04.03 23:33:27 LOG7[24792:140152610346752]: Service extranet.serviceplus-hse.com finished (0 left) 2012.04.03 23:33:27 LOG7[24792:140152610629408]: local socket: FD=0 allocated (non-blocking mode) 2012.04.03 23:33:27 LOG7[24792:140152610629408]: Service extranet.serviceplus-hse.com accepted FD=0 from 82.224.128.241:52123 2012.04.03 23:33:27 LOG7[24792:140152610346752]: Service extranet.serviceplus-hse.com started 2012.04.03 23:33:27 LOG7[24792:140152610346752]: Option TCP_NODELAY set on local socket 2012.04.03 23:33:27 LOG7[24792:140152610346752]: Waiting for a libwrap process 2012.04.03 23:33:27 LOG7[24792:140152610346752]: Acquired libwrap process #0 2012.04.03 23:33:27 LOG7[24792:140152610346752]: Releasing libwrap process #0 2012.04.03 23:33:27 LOG7[24792:140152610346752]: Released libwrap process #0 2012.04.03 23:33:27 LOG7[24792:140152610346752]: Service extranet.serviceplus-hse.com permitted by libwrap from 82.224.128.241:52123 2012.04.03 23:33:27 LOG5[24792:140152610346752]: Service extranet.serviceplus-hse.com accepted connection from 82.224.128.241:52123 2012.04.03 23:33:27 LOG7[24792:140152610346752]: SSL state (accept): before/accept initialization 2012.04.03 23:33:27 LOG7[24792:140152610346752]: SSL state (accept): SSLv3 read client hello B 2012.04.03 23:33:27 LOG7[24792:140152610346752]: SSL state (accept): SSLv3 write server hello A 2012.04.03 23:33:27 LOG7[24792:140152610346752]: SSL state (accept): SSLv3 write change cipher spec A 2012.04.03 23:33:27 LOG7[24792:140152610346752]: SSL state (accept): SSLv3 write finished A 2012.04.03 23:33:27 LOG7[24792:140152610346752]: SSL state (accept): SSLv3 flush data 2012.04.03 23:33:28 LOG7[24792:140152610346752]: SSL state (accept): SSLv3 read finished A 2012.04.03 23:33:28 LOG7[24792:140152610346752]: 7 items in the session cache 2012.04.03 23:33:28 LOG7[24792:140152610346752]: 0 client connects (SSL_connect()) 2012.04.03 23:33:28 LOG7[24792:140152610346752]: 0 client connects that finished 2012.04.03 23:33:28 LOG7[24792:140152610346752]: 0 client renegotiations requested 2012.04.03 23:33:28 LOG7[24792:140152610346752]: 22 server connects (SSL_accept()) 2012.04.03 23:33:28 LOG7[24792:140152610346752]: 21 server connects that finished 2012.04.03 23:33:28 LOG7[24792:140152610346752]: 0 server renegotiations requested 2012.04.03 23:33:28 LOG7[24792:140152610346752]: 10 session cache hits 2012.04.03 23:33:28 LOG7[24792:140152610346752]: 0 external session cache hits 2012.04.03 23:33:28 LOG7[24792:140152610346752]: 7 session cache misses 2012.04.03 23:33:28 LOG7[24792:140152610346752]: 4 session cache timeouts 2012.04.03 23:33:28 LOG6[24792:140152610346752]: SSL accepted: previous session reused 2012.04.03 23:33:28 LOG7[24792:140152610346752]: remote socket: FD=1 allocated (non-blocking mode) 2012.04.03 23:33:28 LOG6[24792:140152610346752]: connect_blocking: connecting 127.0.0.1:82 2012.04.03 23:33:28 LOG7[24792:140152610346752]: connect_blocking: s_poll_wait 127.0.0.1:82: waiting 10 seconds 2012.04.03 23:33:28 LOG5[24792:140152610346752]: connect_blocking: connected 127.0.0.1:82 2012.04.03 23:33:28 LOG5[24792:140152610346752]: Service extranet.serviceplus-hse.com connected remote server from 127.0.0.1:36256 2012.04.03 23:33:28 LOG7[24792:140152610346752]: Remote FD=1 initialized 2012.04.03 23:33:28 LOG7[24792:140152610346752]: Option TCP_NODELAY set on remote socket 2012.04.03 23:33:41 LOG7[24792:140152610346752]: Socket closed on read 2012.04.03 23:33:41 LOG7[24792:140152610346752]: Sending SSL write shutdown 2012.04.03 23:33:41 LOG7[24792:140152610346752]: SSL alert (write): warning: close notify 2012.04.03 23:33:41 LOG6[24792:140152610346752]: SSL_shutdown successfully sent close_notify 2012.04.03 23:33:41 LOG3[24792:140152610346752]: transfer: s_poll_wait: TIMEOUTclose exceeded: closing 2012.04.03 23:33:41 LOG5[24792:140152610346752]: Connection closed: 186584 bytes sent to SSL, 3275 bytes sent to socket 2012.04.03 23:33:41 LOG7[24792:140152610346752]: Service extranet.serviceplus-hse.com finished (0 left) 2012.04.04 06:25:04 LOG7[24792:140152610629408]: Dispatching signals from the signal pipe ######################################################################

2 6

Ubuntu version of stunnel : multiple process shown by a ps -edf, compiled from sources : one process
by Thomas Manson 08 Apr '12

08 Apr '12

Hi, To get around a bug of stunnel present in the package of Ubuntu 11.10 (that has been corrected in v4.38), I've compiled from sources (v4.53). It went well, but I did notice a change in the processes : from compiled sources, I can see only on process per conf file ###################################################################### 1 21402 21402 21402 ? -1 Ss 109 0:00 /usr/local/bin/stunnel4 /etc/stunnel/base.conf 1 21411 21411 21411 ? -1 Ss 109 0:00 /usr/local/bin/stunnel4 /etc/stunnel/extranet.serviceplus-hse.com.conf 1 21420 21420 21420 ? -1 Ss 109 0:00 /usr/local/bin/stunnel4 /etc/stunnel/mansonthomas.com.conf ###################################################################### while on the ubuntu version, I've multiple process per conf file. ps -edf from ubuntu distrib ###################################################################### 1 24773 24762 18168 ? -1 S 109 0:00 /usr/bin/stunnel4 /etc/stunnel/base.conf 1 24774 24762 18168 ? -1 S 109 0:00 /usr/bin/stunnel4 /etc/stunnel/base.conf 1 24775 24762 18168 ? -1 S 109 0:00 /usr/bin/stunnel4 /etc/stunnel/base.conf 1 24776 24762 18168 ? -1 S 109 0:00 /usr/bin/stunnel4 /etc/stunnel/base.conf 1 24777 24762 18168 ? -1 S 109 0:00 /usr/bin/stunnel4 /etc/stunnel/base.conf 1 24778 24778 24778 ? -1 Ss 109 0:00 /usr/bin/stunnel4 /etc/stunnel/base.conf 1 24787 24762 18168 ? -1 S 109 0:00 /usr/bin/stunnel4 /etc/stunnel/extranet.serviceplus-hse.com.conf 1 24788 24762 18168 ? -1 S 109 0:00 /usr/bin/stunnel4 /etc/stunnel/extranet.serviceplus-hse.com.conf 1 24789 24762 18168 ? -1 S 109 0:00 /usr/bin/stunnel4 /etc/stunnel/extranet.serviceplus-hse.com.conf 1 24790 24762 18168 ? -1 S 109 0:00 /usr/bin/stunnel4 /etc/stunnel/extranet.serviceplus-hse.com.conf 1 24791 24762 18168 ? -1 S 109 0:00 /usr/bin/stunnel4 /etc/stunnel/extranet.serviceplus-hse.com.conf 1 24792 24792 24792 ? -1 Ss 109 0:00 /usr/bin/stunnel4 /etc/stunnel/extranet.serviceplus-hse.com.conf 1 24801 24762 18168 ? -1 S 109 0:00 /usr/bin/stunnel4 /etc/stunnel/mansonthomas.com.conf 1 24802 24762 18168 ? -1 S 109 0:00 /usr/bin/stunnel4 /etc/stunnel/mansonthomas.com.conf 1 24803 24762 18168 ? -1 S 109 0:00 /usr/bin/stunnel4 /etc/stunnel/mansonthomas.com.conf 1 24804 24762 18168 ? -1 S 109 0:00 /usr/bin/stunnel4 /etc/stunnel/mansonthomas.com.conf 1 24805 24762 18168 ? -1 S 109 0:00 /usr/bin/stunnel4 /etc/stunnel/mansonthomas.com.conf 1 24806 24806 24806 ? -1 Ss 109 0:00 /usr/bin/stunnel4 /etc/stunnel/mansonthomas.com.conf ###################################################################### I'm using the exact same version of conf file for both setup... any idea why this change ? is one better than another ? Regards, Thomas.

1 0

Transparent STunnel & HAProxy on Centos6.2
by Scott McKeown 07 Apr '12

07 Apr '12

Hi All, I've been playing with this for a little while now and before the all in front of me and my head meet I was wondering if someone else could shed some light on this for me please. First off let me give you a over view of the network setup: My Virtual Machine has two interfaces eth0 has two addresses 192.168.82.9/18and 192.168.82.10/18. 192.168.82.9 is going to be for the management of the server and 192.168.82.10 is what the website will respond too. eth1 has a network of its own 10.0.0.0/24 and I have two Debian Apache web servers that are connected to this network 10.0.0.10 and 10.0.0.20. If this was a real world setup I might have put the management address (192.168.82.9) on a different port but I didn't think of that at the time of setting this up but I may do that later. Second what have I done! Well this is a brand new install of Centos6.2 minimal fully patched and both HAProxy and STunnel downloaded and installed. I'm using the devel version of HAProxy but thats a different story and version 4.53 of STunnel. Now the problem. Both seem to work perfectly as-long as I don't want to know who is accessing my site which make it next to useless. However, I can get HAProxy to report the IP Address of the visitor as long as you visit the HTTP page on port 80 as per my configuration file. I can also get STunnel to work with HAProxy but as soon as I enable 'protocol = proxy' the HTTPS side breaks and all I get in my browser is '400 Bad Request Your browser sent an invalid request'. I've played with everything I can thing of and I still cant get a Transparent STunnel>HAProxy solution working correctly. Config Files: stunnel.conf ====================================== chroot = /usr/local/var/lib/stunnel/ #setuid = nobody setgid = nobody pid = /stunnel.pid cert = /usr/local/etc/stunnel/stunnel.pem key = /usr/local/etc/stunnel/stunnel.pem options = NO_SSLv2 debug = 7 #fips = no [https] accept = 192.168.82.10:443 connect = 192.168.82.10:80 protocol = proxy haproxy.cfg ====================================== global daemon log /dev/log local4 maxconn 40000 ulimit-n 81000 defaults log global mode http contimeout 4000 clitimeout 42000 srvtimeout 43000 listen http1 bind 192.168.82.10:80 mode http option http-server-close option forwardfor source 0.0.0.0 usesrc clientip balance roundrobin server http1_1 10.0.0.10:80 cookie http1_1 check inter 2000 rise 2 fall 3 server http1_1 10.0.0.20:80 cookie http1_1 check inter 2000 rise 2 fall 3 Log file ====================================== Apr 5 12:37:32 lbmaster haproxy[1351]: Proxy http1 started. Apr 5 12:37:33 lbmaster stunnel: LOG5[1353:140163149080512]: stunnel 4.53 on x86_64-unknown-linux-gnu platform Apr 5 12:37:33 lbmaster stunnel: LOG5[1353:140163149080512]: Compiled/running with OpenSSL 1.0.0-fips 29 Mar 2010 Apr 5 12:37:33 lbmaster stunnel: LOG5[1353:140163149080512]: Threading:PTHREAD SSL:+ENGINE+OCSP+FIPS Auth:none Sockets:POLL+IPv6 Apr 5 12:37:33 lbmaster stunnel: LOG5[1353:140163149080512]: Reading configuration from file /usr/local/etc/stunnel/stunnel.conf Apr 5 12:37:33 lbmaster stunnel: LOG5[1353:140163149080512]: FIPS mode is enabled Apr 5 12:37:33 lbmaster stunnel: LOG6[1353:140163149080512]: Initializing service section [https] Apr 5 12:37:33 lbmaster stunnel: LOG5[1353:140163149080512]: Configuration successful Apr 5 12:37:41 lbmaster stunnel: LOG5[1354:140163149076224]: Service [https] accepted connection from 192.168.64.10:53149 Apr 5 12:37:41 lbmaster stunnel: LOG6[1354:140163149076224]: connect_blocking: connecting 192.168.82.10:80 Apr 5 12:37:41 lbmaster haproxy[1352]: Connect from 192.168.82.10:47570 to 192.168.82.10:80 (http1/HTTP) Apr 5 12:37:41 lbmaster stunnel: LOG5[1354:140163149076224]: connect_blocking: connected 192.168.82.10:80 Apr 5 12:37:41 lbmaster stunnel: LOG5[1354:140163149076224]: Service [https] connected remote server from 192.168.82.10:47570 Apr 5 12:37:41 lbmaster stunnel: LOG6[1354:140163149076224]: Server-mode proxy protocol negotiations started Apr 5 12:37:41 lbmaster stunnel: LOG6[1354:140163149076224]: Server-mode proxy protocol negotiations succeeded Apr 5 12:37:41 lbmaster stunnel: LOG6[1354:140163149076224]: SSL accepted: new session negotiated Apr 5 12:37:41 lbmaster stunnel: LOG6[1354:140163149076224]: Negotiated TLSv1/SSLv3 ciphersuite: DHE-RSA-AES256-SHA (256-bit encryption) Apr 5 12:37:41 lbmaster stunnel: LOG6[1354:140163149076224]: Compression: null, expansion: null Apr 5 12:37:41 lbmaster stunnel: LOG6[1354:140163149076224]: SSL_shutdown successfully sent close_notify alert Apr 5 12:37:41 lbmaster stunnel: LOG5[1354:140163149076224]: Error detected on socket (read) file descriptor: Broken pipe (32) Apr 5 12:37:41 lbmaster stunnel: LOG5[1354:140163149076224]: Connection reset: 187 byte(s) sent to SSL, 1 byte(s) sent to socket Any help would be most gracefully received and welcome. ~Yours, Scott

2 1

help
by Bill Tindal 07 Apr '12

07 Apr '12

On Sat, Apr 7, 2012 at 8:00 PM, <stunnel-users-request(a)stunnel.org> wrote: > Send stunnel-users mailing list submissions to > stunnel-users(a)stunnel.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://stunnel.mirt.net/mailman/listinfo/stunnel-users > or, via email, send a message with subject or body 'help' to > stunnel-users-request(a)stunnel.org > > You can reach the person managing the list at > stunnel-users-owner(a)stunnel.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of stunnel-users digest..." > > > Today's Topics: > > 1. Re: [Stunnel Guru needed] stunnel running, but no longer > serve connection after a while ("Dispatching signals from the > signal pipe" in logs ==> all stops) (Thomas Manson) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 7 Apr 2012 08:24:46 +0200 > From: Thomas Manson <dev.mansonthomas(a)gmail.com> > To: Scott Gifford <sgifford(a)suspectclass.com> > Cc: stunnel-users(a)stunnel.org > Subject: Re: [stunnel-users] [Stunnel Guru needed] stunnel running, > but no longer serve connection after a while ("Dispatching signals > from the signal pipe" in logs ==> all stops) > Message-ID: > <CA+PenvGYr+tTiKsavOgyaLOtoRxUo0nfxuRVDEzdvGDrFpefLg(a)mail.gmail.com > > > Content-Type: text/plain; charset="utf-8" > > This bug has been corrected in > > Version 4.38, 2011.06.28, urgency: MEDIUM: > > - New features > - Server-side SNI implemented (RFC 3546 section 3.1) with a new > service-level option "nsi". > - "socket" option also accepts "yes" and "no" for flags. > - Nagle's algorithm is now disabled by default for improved > interactivity. > - Bugfixes > - A compilation fix was added for OpenSSL version < 1.0.0. > - Signal pipe set to non-blocking mode. This bug caused hangs of > stunnel features based on signals, e.g. local mode, FORK threading, or > configuration file reload on Unix. Win32 platform was not affected. > > > however it don't precise from which version it affects stunnel... so my try > with 11.04 is a bit risky, even if 4.29 is quite far from 4.38. > > Maybe upgrading to 12.04 could solve the issue, but I don't like to upgrade > right away (I had some bad surpise ;)) > > so compiling from source seems to be the safest option. > > Thomas. > > On Sat, Apr 7, 2012 at 07:58, Thomas Manson <dev.mansonthomas(a)gmail.com > >wrote: > > > i've just checked my setup right now and the funny thing is that I think > > it stopped working exactly at the same second of the same hour & minute > of > > the day : > > > > > > root@ns0:/var/log/stunnel4# ll > > total 940 > > drwxr-xr-x 2 stunnel4 stunnel4 4096 2012-04-07 06:25 . > > drwxr-xr-x 14 root root 4096 2012-04-07 06:25 .. > > -rw-r----- 1 stunnel4 stunnel4 0 2012-04-07 06:25 > > extranet.serviceplus-hse.com_stunnel.log > > -rw-r----- 1 stunnel4 stunnel4 926267 2012-04-07 06:25 > > extranet.serviceplus-hse.com_stunnel.log.1 > > -rw-r----- 1 stunnel4 stunnel4 0 2012-04-07 06:25 > > mansonthomas.com_stunnel.log > > -rw-r----- 1 stunnel4 stunnel4 5804 2012-04-07 06:25 > > mansonthomas.com_stunnel.log.1 > > -rw-r----- 1 stunnel4 stunnel4 0 2012-04-07 06:25 stunnel.log > > -rw-r----- 1 stunnel4 stunnel4 11710 2012-04-07 06:25 stunnel.log.1 > > root@ns0:/var/log/stunnel4# ll > > total 940 > > drwxr-xr-x 2 stunnel4 stunnel4 4096 2012-04-07 06:25 . > > drwxr-xr-x 14 root root 4096 2012-04-07 06:25 .. > > -rw-r----- 1 stunnel4 stunnel4 0 2012-04-07 06:25 > > extranet.serviceplus-hse.com_stunnel.log > > -rw-r----- 1 stunnel4 stunnel4 926267 2012-04-07 06:25 > > extranet.serviceplus-hse.com_stunnel.log.1 > > -rw-r----- 1 stunnel4 stunnel4 0 2012-04-07 06:25 > > mansonthomas.com_stunnel.log > > -rw-r----- 1 stunnel4 stunnel4 5804 2012-04-07 06:25 > > mansonthomas.com_stunnel.log.1 > > -rw-r----- 1 stunnel4 stunnel4 0 2012-04-07 06:25 stunnel.log > > -rw-r----- 1 stunnel4 stunnel4 11710 2012-04-07 06:25 stunnel.log.1 > > root@ns0:/var/log/stunnel4# tail stunnel.log.1 > > 2012.04.06 22:21:19 LOG7[4745:139677248579328]: Option TCP_NODELAY set > on > > remote socket > > 2012.04.06 22:21:19 LOG7[4745:139677248579328]: Socket closed on read > > 2012.04.06 22:21:19 LOG7[4745:139677248579328]: Sending SSL write > shutdown > > 2012.04.06 22:21:19 LOG7[4745:139677248579328]: SSL alert (write): > > warning: close notify > > 2012.04.06 22:21:19 LOG6[4745:139677248579328]: SSL_shutdown > successfully > > sent close_notify > > 2012.04.06 22:21:19 LOG7[4745:139677248579328]: SSL socket closed on > > SSL_read > > 2012.04.06 22:21:19 LOG7[4745:139677248579328]: Sending socket write > > shutdown > > 2012.04.06 22:21:19 LOG5[4745:139677248579328]: Connection closed: 206 > > bytes sent to SSL, 139 bytes sent to socket > > 2012.04.06 22:21:19 LOG7[4745:139677248579328]: Service > > https-123monsite.com finished (0 left) > > 2012.04.07 06:25:04 LOG7[4745:139677248583456]: Dispatching signals from > > the signal pipe > > root@ns0:/var/log/stunnel4# > > > > compared to my first post... : > > > > > > > > > > - 2012.04.04 06:25:04 LOG7[24778:139641780213536]: Dispatching > signals > > from the signal pipe > > - > > and at the same time (2012.04.04 06:25:04) all logs file stops : > > > > > > - root@ns0:/var/log/stunnel4# ll > > - total 128 > > - drwxr-xr-x 2 stunnel4 stunnel4 4096 2012-04-04 12:10 . > > - drwxr-xr-x 14 root root 4096 2012-04-04 06:25 .. > > - -rw-r----- 1 stunnel4 stunnel4 98084 2012-04-04 *06:25* > > extranet.serviceplus-hse.com_stunnel.log > > - -rw-r----- 1 stunnel4 stunnel4 4491 2012-04-04 06:25 > > mansonthomas.com_stunnel.log > > - -rw-r----- 1 stunnel4 stunnel4 0 2012-04-04 06:25 stunnel.log > > - -rw-r----- 1 stunnel4 stunnel4 11058 2012-04-04 06:25 stunnel.log.1 > > > > > > > > I could cron a restart at the appropriate time but I think I'll compile > > from sources. > > > > Regards, > > Thomas. > > > > On Sat, Apr 7, 2012 at 07:51, Thomas Manson <dev.mansonthomas(a)gmail.com > >wrote: > > > >> Yes, it helps a lot ! > >> > >> I've another server running a different version of Ubuntu (11.04 where > >> stunnel version is 4.29-1 instead of 11.10 and stunnel 4.35-2build1) > >> > >> Do you think it can work on older version ? > >> > >> I was thinking to try this because I've seen some message about the same > >> symptoms after upgrade so... > >> > >> but maybe the two version are too close and I will need to compile from > >> sources... > >> > >> what do you think about this? > >> > >> Regards, > >> Thomas. > >> > >> > >> On Sat, Apr 7, 2012 at 06:56, Scott Gifford <sgifford(a)suspectclass.com > >wrote: > >> > >>> On Wed, Apr 4, 2012 at 6:16 AM, Thomas Manson < > >>> dev.mansonthomas(a)gmail.com> wrote: > >>> > >>>> Hi All, > >>>> > >>>> I'm really struggling to make stunnel working for more than a few > >>>> hours. (and the client is yelling hard...) (I solved some other issue > : > >>>> logging per website and making more than one stunnel works) > >>>> > >>> > >>> Hi Thomas, > >>> > >>> I was just troubleshooting what looks like a very similar issue. I > >>> believe this is fixed in a later version of stunnel, which you can get > from > >>> stunnel.org and compile yourself from source. > >>> > >>> This is the ChangeLog entry that I think addresses your problem: > >>> > >>> - Signal pipe set to non-blocking mode. This bug caused hangs of > >>> stunnel > >>> features based on signals, e.g. local mode, FORK threading, or > >>> configuration file reload on Unix. Win32 platform was not > affected. > >>> > >>> > >>> I have just updated from the official Oneiric version to this one, so I > >>> don't yet know if it will fix the problem long-term, but I think my > odds > >>> are not too bad. > >>> > >>> Hope this helps, > >>> > >>> -----Scott. > >>> > >>> > >> > > >

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