- stunnel-users - stunnel.org

win32 help
by chris rheinherren 28 Jun '05

28 Jun '05

I am running a win32 based IRC server and I wanted to add SSL to it. I have stunnel up and running. I have the necessary dlls installed. And I have found various help pages on creating the config file. And lastly my irc client is capable of connecting to SSL based servers. so here is my config file: <---- beging ------> RNDfile = C:\stunnel-prnd.txt RNDoverwrite = yes debug = 7 output = C:\stunnel.log [irc] accept = 66.98.154.87:994 connect = 127.0.0.1:994 <---- ending -----> And here is the log outup to help figure out what is wrong as well. <---- log -----> 2005.06.27 21:38:46 LOG5[2364:4084]: stunnel 4.04 on x86-pc-mingw32-gnu WIN32 with OpenSSL 0.9.7c 30 Sep 2003 2005.06.27 21:38:46 LOG7[2364:3120]: RAND_status claims sufficient entropy for the PRNG 2005.06.27 21:38:46 LOG6[2364:3120]: PRNG seeded successfully 2005.06.27 21:38:46 LOG7[2364:3120]: Certificate: stunnel.pem 2005.06.27 21:38:46 LOG7[2364:3120]: Key file: stunnel.pem 2005.06.27 21:38:46 LOG5[2364:3120]: WIN32 platform: 30000 clients allowed 2005.06.27 21:38:46 LOG7[2364:3120]: FD 132 in non-blocking mode 2005.06.27 21:38:46 LOG7[2364:3120]: SO_REUSEADDR option set on accept socket 2005.06.27 21:38:46 LOG7[2364:3120]: irc bound to 66.98.154.87:994 2005.06.27 21:39:43 LOG7[2364:3120]: irc accepted FD=144 from 12.216.55.121:1583 2005.06.27 21:39:43 LOG7[2364:3120]: FD 144 in non-blocking mode 2005.06.27 21:39:43 LOG7[2364:396]: irc started 2005.06.27 21:39:43 LOG5[2364:396]: irc connected from 12.216.55.121:1583 2005.06.27 21:39:43 LOG7[2364:396]: SSL state (accept): before/accept initialization 2005.06.27 21:39:43 LOG7[2364:396]: waitforsocket: FD=144, DIR=read 2005.06.27 21:39:43 LOG7[2364:396]: waitforsocket: ok 2005.06.27 21:39:43 LOG7[2364:396]: SSL state (accept): SSLv3 read client hello A 2005.06.27 21:39:43 LOG7[2364:396]: SSL state (accept): SSLv3 write server hello A 2005.06.27 21:39:43 LOG7[2364:396]: SSL state (accept): SSLv3 write certificate A 2005.06.27 21:39:43 LOG7[2364:396]: SSL state (accept): SSLv3 write server done A 2005.06.27 21:39:43 LOG7[2364:396]: SSL state (accept): SSLv3 flush data 2005.06.27 21:39:43 LOG7[2364:396]: waitforsocket: FD=144, DIR=read 2005.06.27 21:39:43 LOG7[2364:396]: waitforsocket: ok 2005.06.27 21:39:43 LOG7[2364:396]: SSL state (accept): SSLv3 read client key exchange A 2005.06.27 21:39:43 LOG7[2364:396]: SSL state (accept): SSLv3 read finished A 2005.06.27 21:39:43 LOG7[2364:396]: SSL state (accept): SSLv3 write change cipher spec A 2005.06.27 21:39:43 LOG7[2364:396]: SSL state (accept): SSLv3 write finished A 2005.06.27 21:39:43 LOG7[2364:396]: SSL state (accept): SSLv3 flush data 2005.06.27 21:39:43 LOG7[2364:396]: 1 items in the session cache 2005.06.27 21:39:43 LOG7[2364:396]: 0 client connects (SSL_connect()) 2005.06.27 21:39:43 LOG7[2364:396]: 0 client connects that finished 2005.06.27 21:39:43 LOG7[2364:396]: 0 client renegotiatations requested 2005.06.27 21:39:43 LOG7[2364:396]: 1 server connects (SSL_accept()) 2005.06.27 21:39:43 LOG7[2364:396]: 1 server connects that finished 2005.06.27 21:39:43 LOG7[2364:396]: 0 server renegotiatiations requested 2005.06.27 21:39:43 LOG7[2364:396]: 0 session cache hits 2005.06.27 21:39:43 LOG7[2364:396]: 0 session cache misses 2005.06.27 21:39:43 LOG7[2364:396]: 0 session cache timeouts 2005.06.27 21:39:43 LOG6[2364:396]: Negotiated ciphers: AES256-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA1 2005.06.27 21:39:43 LOG7[2364:396]: FD 164 in non-blocking mode 2005.06.27 21:39:43 LOG7[2364:396]: irc connecting 127.0.0.1:994 2005.06.27 21:39:43 LOG7[2364:396]: remote connect #1: EWOULDBLOCK: retrying 2005.06.27 21:39:43 LOG7[2364:396]: waitforsocket: FD=164, DIR=write 2005.06.27 21:44:43 LOG7[2364:396]: waitforsocket: timeout 2005.06.27 21:44:43 LOG3[2364:396]: Failed to initialize remote connection 2005.06.27 21:44:43 LOG7[2364:396]: irc finished (0 left) 2005.06.27 21:44:47 LOG7[2364:3120]: irc accepted FD=180 from 12.216.55.121:1639 2005.06.27 21:44:47 LOG7[2364:3120]: FD 180 in non-blocking mode 2005.06.27 21:44:47 LOG7[2364:768]: irc started 2005.06.27 21:44:47 LOG5[2364:768]: irc connected from 12.216.55.121:1639 2005.06.27 21:44:47 LOG7[2364:768]: SSL state (accept): before/accept initialization 2005.06.27 21:44:47 LOG7[2364:768]: waitforsocket: FD=180, DIR=read 2005.06.27 21:44:47 LOG7[2364:768]: waitforsocket: ok 2005.06.27 21:44:47 LOG7[2364:768]: SSL state (accept): SSLv3 read client hello A 2005.06.27 21:44:47 LOG7[2364:768]: SSL state (accept): SSLv3 write server hello A 2005.06.27 21:44:47 LOG7[2364:768]: SSL state (accept): SSLv3 write certificate A 2005.06.27 21:44:47 LOG7[2364:768]: SSL state (accept): SSLv3 write server done A 2005.06.27 21:44:47 LOG7[2364:768]: SSL state (accept): SSLv3 flush data 2005.06.27 21:44:47 LOG7[2364:768]: waitforsocket: FD=180, DIR=read 2005.06.27 21:44:47 LOG7[2364:768]: waitforsocket: ok 2005.06.27 21:44:47 LOG7[2364:768]: SSL state (accept): SSLv3 read client key exchange A 2005.06.27 21:44:47 LOG7[2364:768]: SSL state (accept): SSLv3 read finished A 2005.06.27 21:44:47 LOG7[2364:768]: SSL state (accept): SSLv3 write change cipher spec A 2005.06.27 21:44:47 LOG7[2364:768]: SSL state (accept): SSLv3 write finished A 2005.06.27 21:44:47 LOG7[2364:768]: SSL state (accept): SSLv3 flush data 2005.06.27 21:44:47 LOG7[2364:768]: 2 items in the session cache 2005.06.27 21:44:47 LOG7[2364:768]: 0 client connects (SSL_connect()) 2005.06.27 21:44:47 LOG7[2364:768]: 0 client connects that finished 2005.06.27 21:44:47 LOG7[2364:768]: 0 client renegotiatations requested 2005.06.27 21:44:47 LOG7[2364:768]: 2 server connects (SSL_accept()) 2005.06.27 21:44:47 LOG7[2364:768]: 2 server connects that finished 2005.06.27 21:44:47 LOG7[2364:768]: 0 server renegotiatiations requested 2005.06.27 21:44:47 LOG7[2364:768]: 0 session cache hits 2005.06.27 21:44:47 LOG7[2364:768]: 0 session cache misses 2005.06.27 21:44:47 LOG7[2364:768]: 0 session cache timeouts 2005.06.27 21:44:47 LOG6[2364:768]: Negotiated ciphers: AES256-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA1 2005.06.27 21:44:47 LOG7[2364:768]: FD 148 in non-blocking mode 2005.06.27 21:44:47 LOG7[2364:768]: irc connecting 127.0.0.1:994 2005.06.27 21:44:47 LOG7[2364:768]: remote connect #1: EWOULDBLOCK: retrying 2005.06.27 21:44:47 LOG7[2364:768]: waitforsocket: FD=148, DIR=write 2005.06.27 21:49:47 LOG7[2364:768]: waitforsocket: timeout 2005.06.27 21:49:47 LOG3[2364:768]: Failed to initialize remote connection 2005.06.27 21:49:47 LOG7[2364:768]: irc finished (0 left) 2005.06.27 21:49:51 LOG7[2364:3120]: irc accepted FD=168 from 12.216.55.121:1689 2005.06.27 21:49:51 LOG7[2364:3120]: FD 168 in non-blocking mode 2005.06.27 21:49:51 LOG7[2364:2508]: irc started 2005.06.27 21:49:51 LOG5[2364:2508]: irc connected from 12.216.55.121:1689 2005.06.27 21:49:51 LOG7[2364:2508]: SSL state (accept): before/accept initialization 2005.06.27 21:49:51 LOG7[2364:2508]: waitforsocket: FD=168, DIR=read 2005.06.27 21:49:51 LOG7[2364:2508]: waitforsocket: ok 2005.06.27 21:49:51 LOG7[2364:2508]: SSL state (accept): SSLv3 read client hello A 2005.06.27 21:49:51 LOG7[2364:2508]: SSL state (accept): SSLv3 write server hello A 2005.06.27 21:49:51 LOG7[2364:2508]: SSL state (accept): SSLv3 write certificate A 2005.06.27 21:49:51 LOG7[2364:2508]: SSL state (accept): SSLv3 write server done A 2005.06.27 21:49:51 LOG7[2364:2508]: SSL state (accept): SSLv3 flush data 2005.06.27 21:49:51 LOG7[2364:2508]: waitforsocket: FD=168, DIR=read 2005.06.27 21:49:51 LOG7[2364:2508]: waitforsocket: ok 2005.06.27 21:49:51 LOG7[2364:2508]: SSL state (accept): SSLv3 read client key exchange A 2005.06.27 21:49:51 LOG7[2364:2508]: SSL state (accept): SSLv3 read finished A 2005.06.27 21:49:51 LOG7[2364:2508]: SSL state (accept): SSLv3 write change cipher spec A 2005.06.27 21:49:51 LOG7[2364:2508]: SSL state (accept): SSLv3 write finished A 2005.06.27 21:49:51 LOG7[2364:2508]: SSL state (accept): SSLv3 flush data 2005.06.27 21:49:51 LOG7[2364:2508]: 3 items in the session cache 2005.06.27 21:49:51 LOG7[2364:2508]: 0 client connects (SSL_connect()) 2005.06.27 21:49:51 LOG7[2364:2508]: 0 client connects that finished 2005.06.27 21:49:51 LOG7[2364:2508]: 0 client renegotiatations requested 2005.06.27 21:49:51 LOG7[2364:2508]: 3 server connects (SSL_accept()) 2005.06.27 21:49:51 LOG7[2364:2508]: 3 server connects that finished 2005.06.27 21:49:51 LOG7[2364:2508]: 0 server renegotiatiations requested 2005.06.27 21:49:51 LOG7[2364:2508]: 0 session cache hits 2005.06.27 21:49:51 LOG7[2364:2508]: 0 session cache misses 2005.06.27 21:49:51 LOG7[2364:2508]: 0 session cache timeouts 2005.06.27 21:49:51 LOG6[2364:2508]: Negotiated ciphers: AES256-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA1 2005.06.27 21:49:51 LOG7[2364:2508]: FD 156 in non-blocking mode 2005.06.27 21:49:51 LOG7[2364:2508]: irc connecting 127.0.0.1:994 2005.06.27 21:49:51 LOG7[2364:2508]: remote connect #1: EWOULDBLOCK: retrying 2005.06.27 21:49:51 LOG7[2364:2508]: waitforsocket: FD=156, DIR=write 2005.06.27 21:54:51 LOG7[2364:2508]: waitforsocket: timeout 2005.06.27 21:54:51 LOG3[2364:2508]: Failed to initialize remote connection 2005.06.27 21:54:51 LOG7[2364:2508]: irc finished (0 left) 2005.06.27 21:54:55 LOG7[2364:3120]: irc accepted FD=164 from 12.216.55.121:1747 2005.06.27 21:54:55 LOG7[2364:3120]: FD 164 in non-blocking mode 2005.06.27 21:54:55 LOG7[2364:460]: irc started 2005.06.27 21:54:55 LOG5[2364:460]: irc connected from 12.216.55.121:1747 2005.06.27 21:54:55 LOG7[2364:460]: SSL state (accept): before/accept initialization 2005.06.27 21:54:55 LOG7[2364:460]: SSL state (accept): SSLv3 read client hello A 2005.06.27 21:54:55 LOG7[2364:460]: SSL state (accept): SSLv3 write server hello A 2005.06.27 21:54:55 LOG7[2364:460]: SSL state (accept): SSLv3 write certificate A 2005.06.27 21:54:55 LOG7[2364:460]: SSL state (accept): SSLv3 write server done A 2005.06.27 21:54:55 LOG7[2364:460]: SSL state (accept): SSLv3 flush data 2005.06.27 21:54:55 LOG7[2364:460]: waitforsocket: FD=164, DIR=read 2005.06.27 21:54:55 LOG7[2364:460]: waitforsocket: ok 2005.06.27 21:54:55 LOG7[2364:460]: SSL state (accept): SSLv3 read client key exchange A 2005.06.27 21:54:55 LOG7[2364:460]: SSL state (accept): SSLv3 read finished A 2005.06.27 21:54:55 LOG7[2364:460]: SSL state (accept): SSLv3 write change cipher spec A 2005.06.27 21:54:55 LOG7[2364:460]: SSL state (accept): SSLv3 write finished A 2005.06.27 21:54:55 LOG7[2364:460]: SSL state (accept): SSLv3 flush data 2005.06.27 21:54:55 LOG7[2364:460]: 4 items in the session cache 2005.06.27 21:54:55 LOG7[2364:460]: 0 client connects (SSL_connect()) 2005.06.27 21:54:55 LOG7[2364:460]: 0 client connects that finished 2005.06.27 21:54:55 LOG7[2364:460]: 0 client renegotiatations requested 2005.06.27 21:54:55 LOG7[2364:460]: 4 server connects (SSL_accept()) 2005.06.27 21:54:55 LOG7[2364:460]: 4 server connects that finished 2005.06.27 21:54:55 LOG7[2364:460]: 0 server renegotiatiations requested 2005.06.27 21:54:55 LOG7[2364:460]: 0 session cache hits 2005.06.27 21:54:55 LOG7[2364:460]: 0 session cache misses 2005.06.27 21:54:55 LOG7[2364:460]: 0 session cache timeouts 2005.06.27 21:54:55 LOG6[2364:460]: Negotiated ciphers: AES256-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA1 2005.06.27 21:54:55 LOG7[2364:460]: FD 144 in non-blocking mode 2005.06.27 21:54:55 LOG7[2364:460]: irc connecting 127.0.0.1:994 2005.06.27 21:54:55 LOG7[2364:460]: remote connect #1: EWOULDBLOCK: retrying 2005.06.27 21:54:55 LOG7[2364:460]: waitforsocket: FD=144, DIR=write 2005.06.27 21:59:55 LOG7[2364:460]: waitforsocket: timeout 2005.06.27 21:59:55 LOG3[2364:460]: Failed to initialize remote connection 2005.06.27 21:59:55 LOG7[2364:460]: irc finished (0 left) 2005.06.27 21:59:59 LOG7[2364:3120]: irc accepted FD=148 from 12.216.55.121:1813 2005.06.27 21:59:59 LOG7[2364:3120]: FD 148 in non-blocking mode 2005.06.27 21:59:59 LOG7[2364:2240]: irc started 2005.06.27 21:59:59 LOG5[2364:2240]: irc connected from 12.216.55.121:1813 2005.06.27 21:59:59 LOG7[2364:2240]: SSL state (accept): before/accept initialization 2005.06.27 21:59:59 LOG7[2364:2240]: waitforsocket: FD=148, DIR=read 2005.06.27 21:59:59 LOG7[2364:2240]: waitforsocket: ok 2005.06.27 21:59:59 LOG7[2364:2240]: SSL state (accept): SSLv3 read client hello A 2005.06.27 21:59:59 LOG7[2364:2240]: SSL state (accept): SSLv3 write server hello A 2005.06.27 21:59:59 LOG7[2364:2240]: SSL state (accept): SSLv3 write certificate A 2005.06.27 21:59:59 LOG7[2364:2240]: SSL state (accept): SSLv3 write server done A 2005.06.27 21:59:59 LOG7[2364:2240]: SSL state (accept): SSLv3 flush data 2005.06.27 21:59:59 LOG7[2364:2240]: waitforsocket: FD=148, DIR=read 2005.06.27 21:59:59 LOG7[2364:2240]: waitforsocket: ok 2005.06.27 21:59:59 LOG7[2364:2240]: SSL state (accept): SSLv3 read client key exchange A 2005.06.27 21:59:59 LOG7[2364:2240]: SSL state (accept): SSLv3 read finished A 2005.06.27 21:59:59 LOG7[2364:2240]: SSL state (accept): SSLv3 write change cipher spec A 2005.06.27 21:59:59 LOG7[2364:2240]: SSL state (accept): SSLv3 write finished A 2005.06.27 21:59:59 LOG7[2364:2240]: SSL state (accept): SSLv3 flush data 2005.06.27 21:59:59 LOG7[2364:2240]: 5 items in the session cache 2005.06.27 21:59:59 LOG7[2364:2240]: 0 client connects (SSL_connect()) 2005.06.27 21:59:59 LOG7[2364:2240]: 0 client connects that finished 2005.06.27 21:59:59 LOG7[2364:2240]: 0 client renegotiatations requested 2005.06.27 21:59:59 LOG7[2364:2240]: 5 server connects (SSL_accept()) 2005.06.27 21:59:59 LOG7[2364:2240]: 5 server connects that finished 2005.06.27 21:59:59 LOG7[2364:2240]: 0 server renegotiatiations requested 2005.06.27 21:59:59 LOG7[2364:2240]: 0 session cache hits 2005.06.27 21:59:59 LOG7[2364:2240]: 0 session cache misses 2005.06.27 21:59:59 LOG7[2364:2240]: 0 session cache timeouts 2005.06.27 21:59:59 LOG6[2364:2240]: Negotiated ciphers: AES256-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA1 2005.06.27 21:59:59 LOG7[2364:2240]: FD 180 in non-blocking mode 2005.06.27 21:59:59 LOG7[2364:2240]: irc connecting 127.0.0.1:994 2005.06.27 21:59:59 LOG7[2364:2240]: remote connect #1: EWOULDBLOCK: retrying 2005.06.27 21:59:59 LOG7[2364:2240]: waitforsocket: FD=180, DIR=write <--- end log -----> Any help that gets this working would be great. Thanks

2 1

Re: [stunnel-users] Transparent client IP on Windows
by Michal Trojnara 28 Jun '05

28 Jun '05

"Paul Jones" <jonesy_boy10(a)hotmail.com> wrote: > Apparently this can be enabled on Linux with the -T argument. Does anyone > know if (and how) this is somehow possible on Windows? Implementing a transparent proxy on Windows (Winsock) requires a process to globaly intercept Winsock API function. It's a lame, MSDOS-like solution that I'm not going to support. Best regards, Mike

1 0

Transparent client IP on Windows
by Paul Jones 28 Jun '05

28 Jun '05

Hi all, I've read (and tested for myself) on a few sites that Stunnel does not transparently pass the IP of the connecting client to the server app. My server app thinks all connecting clients are coming from IP 127.0.01. Apparently this can be enabled on Linux with the -T argument. Does anyone know if (and how) this is somehow possible on Windows? Cheers. Paul _________________________________________________________________ REALESTATE: biggest buy/rent/share listings http://ninemsn.realestate.com.au

1 0

Stunnel 4.09 exits unexpected on solaris 2.8
by edonald1＠rochester.rr.com 27 Jun '05

27 Jun '05

Hi, I am running the following version of Stunnel: ./stunnel -version stunnel 4.09 on sparc-sun-solaris2.8 PTHREAD+POLL+IPv4 with OpenSSL 0.9.6m 17 Mar 2004 Global options cert = /apps/stunnel/etc/stunnel/stunnel.pem ciphers = ALL:!ADH:RC4+RSA:+SSLv2:@STRENGTH debug = 5 key = /apps/stunnel/etc/stunnel/stunnel.pem pid = /apps/stunnel/var/run/stunnel.pid RNDbytes = 64 RNDfile = /dev/urandom RNDoverwrite = yes session = 300 seconds verify = none Service-level options TIMEOUTbusy = 300 seconds TIMEOUTclose = 60 seconds TIMEOUTconnect = 10 seconds TIMEOUTidle = 43200 seconds It is compiled with pthreads and without TCPwrappers. I am using it to tunnel a mod_jk connection between apache and tomcat. It works perfectly in my Development and QA environment ( runs for weeks on end). When I moved it to production it started not to work so well. Stunnel would mysterious stop working on the server side (procesd disappears). There are no errors in the log whatsoever and the log level is set at 7. One difference in my production environment is that there are multiple clients (apache) and one server (tomcat). All Thoughts are welcome. Thank You

1 0

Errors sending email thru gmail's smtp server
by Melinda Chin 27 Jun '05

27 Jun '05

Hi, I have written an email client application to send/receive email. However, gmail accounts requires that email clients use SSL. In order to do this, I am running stunnel in the background. I am able to retrieve emails from gmail pop3 server, but I am not able To send email thru gmail smtp server. Gmail requires that email clients Support SMTP authentication, and also requires TLS. I am receiving the following errors in stunnel.log when trying to send email from gmail accounts. Attached is my stunnel.conf file. Is there something I am missing to cause these errors ? Does stunnel support SMTP authentication ? - Melinda 2005.06.27 11:26:17 LOG7[25398:81923]: <- 220 2.0.0 Ready to start TLS. 2005.06.27 11:26:17 LOG7[25398:81923]: SSL state (connect): before/connect initialization 2005.06.27 11:26:17 LOG7[25398:81923]: SSL state (connect): SSLv3 write client hello A 2005.06.27 11:26:17 LOG7[25398:81923]: waitforsocket: FD=13, DIR=read 2005.06.27 11:26:17 LOG7[25398:81923]: waitforsocket: ok 2005.06.27 11:26:17 LOG7[25398:81923]: SSL state (connect): SSLv3 read server hello A 2005.06.27 11:26:17 LOG7[25398:81923]: SSL state (connect): SSLv3 read server certificate A 2005.06.27 11:26:17 LOG7[25398:81923]: SSL state (connect): SSLv3 read server done A 2005.06.27 11:26:17 LOG7[25398:81923]: SSL state (connect): SSLv3 write client key exchange A 2005.06.27 11:26:17 LOG7[25398:81923]: SSL state (connect): SSLv3 write change cipher spec A 2005.06.27 11:26:17 LOG7[25398:81923]: SSL state (connect): SSLv3 write finished A 2005.06.27 11:26:17 LOG7[25398:81923]: SSL state (connect): SSLv3 flush data 2005.06.27 11:26:17 LOG7[25398:81923]: waitforsocket: FD=13, DIR=read 2005.06.27 11:26:17 LOG7[25398:81923]: waitforsocket: ok 2005.06.27 11:26:17 LOG7[25398:81923]: SSL state (connect): SSLv3 read finished A 2005.06.27 11:26:17 LOG7[25398:81923]: 5 items in the session cache 2005.06.27 11:26:17 LOG7[25398:81923]: 5 client connects (SSL_connect()) 2005.06.27 11:26:17 LOG7[25398:81923]: 5 client connects that finished 2005.06.27 11:26:17 LOG7[25398:81923]: 0 client renegotiatations requested 2005.06.27 11:26:17 LOG7[25398:81923]: 0 server connects (SSL_accept()) 2005.06.27 11:26:17 LOG7[25398:81923]: 0 server connects that finished 2005.06.27 11:26:17 LOG7[25398:81923]: 0 server renegotiatiations requested 2005.06.27 11:26:17 LOG7[25398:81923]: 0 session cache hits 2005.06.27 11:26:17 LOG7[25398:81923]: 0 session cache misses 2005.06.27 11:26:17 LOG7[25398:81923]: 0 session cache timeouts 2005.06.27 11:26:17 LOG6[25398:81923]: Negotiated ciphers: DES-CBC3-SHA SSLv3 Kx=RSA Au=RSA Enc=3DES(168) Mac=SHA1 2005.06.27 11:26:18 LOG7[25398:81923]: Socket closed on read 2005.06.27 11:26:18 LOG7[25398:81923]: SSL alert (write): warning: close notify 2005.06.27 11:26:18 LOG7[25398:81923]: SSL write shutdown (output buffer empty) 2005.06.27 11:26:19 LOG7[25398:81923]: SSL socket closed on SSL_read 2005.06.27 11:26:19 LOG5[25398:81923]: Connection closed: 59 bytes sent to SSL, 165 bytes sent to socket 2005.06.27 11:26:19 LOG7[25398:81923]: ssmtp finished (1 left)

1 0

Passphrase validation
by Peter Pentes 27 Jun '05

27 Jun '05

Hi, As I understand it, Stunnel does not currently support the validation of certificate passphrases. For example, to make a connection from the client to the server, no passphrase is requested when a certificate is selected. Are there any plans for this feature to be added to Stunnel? Regards, PP __________________________________ Do you Yahoo!? Make Yahoo! your home page http://www.yahoo.com/r/hs

3 5

Have extra bandwidth. does stunnel need a mirror?
by christopher＠baus.net 27 Jun '05

27 Jun '05

I have extra bandwidth. Does stunnel need a mirror? I'm using stunnel exclusively for my SSL needs. I works great, and I just want to give back. Christopher Baus

3 4

Re: [stunnel-users] Passphrase validation
by Paul Jones 26 Jun '05

26 Jun '05

That's all well and good for a Unix environment, but what about on Windows? No chown or chmod on there! I believe that it is sometimes useful for the passphrase to be requested by Stunnel on startup (on the client side), but you all make valid points. Paul. --- Vasil Dimov <vd(a)datamax.bg> wrote: >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >On Wed, Jun 22, 2005 at 04:30:56PM -0700, Joseph >Mocker wrote: > > > It depends on how the machine were broken. >Presumably if you > > were that hell-bent on using passprhases on >private keys, you'd > > likely isolate stunnel to run as an unpriviledged >user in a chrooted >That is a good idea anyway :) > > > environment, and you may very well set the >coredump size to zero > > and remove a debugger all together. So unless the >user was able > > to break root, the effects of the break-in might >be minimized. > >Private key stealing table: >* the key and the plain text file, holding the >password (if any) > should always be chown root and chmod 400 >* stunnel is the (unprivileged) user stunnel is >running as >* we assume that stunnel is running at the time of >breakage, because > this is the worst case. > > key storage \ break as root stunnel other user >- >--------------------------------------------------------------------------- >1. unencrypted key YES YES NO > >2. crypted key/password in text file YES YES NO > >3. crypted key/password entered at startup YES YES NO >- >--------------------------------------------------------------------------- > >As we see there is no difference if the private key >will be kept >crypted or unencrypted with or without text file >holding the passphrase. > >What happens if the stunnel daemon is not running >during the breakage? >Note that this is an optimistic suggestion and we >should not rely on it. > > key storage \ break as root stunnel other user >- >--------------------------------------------------------------------------- >1. unencrypted key YES NO NO > >2. crypted key/password in text file YES NO NO > >3. crypted key/password entered at startup NO > NO NO >- >--------------------------------------------------------------------------- > >So the only difference in all cases is if stunnel is >not running and the >hacker gets root on the machine and the key is >crypted and the password >is entered at startup - then it will not be possible >to steal the >private key. > >As a conclusion, it is obviously - that there is >really no sense to >keep the password in a text file and it makes a >LITTLE sense if the >password is entered at startup - in just one, rare, >case this setup >will save the private key. > >-----BEGIN PGP SIGNATURE----- > >iD8DBQFCunHRFw6SP/bBpCARAtN4AJ0TBfANXVyyLNKojIaFzb1E/7WBqQCeIcop >rAqsbhJmK9oBYg/Rb9iJzSE= >=rFAJ >-----END PGP SIGNATURE----- >_______________________________________________ >stunnel-users mailing list >stunnel-users(a)mirt.net >http://stunnel.mirt.net/mailman/listinfo/stunnel-users > _________________________________________________________________ Sell your car for $9 on carpoint.com.au http://www.carpoint.com.au/sellyourcar

2 2

4.10 runtime crash (alignment error?) in Solaris 7
by Old Wolf 24 Jun '05

24 Jun '05

When I run stunnel 4.10 with openssl 0.9.8 beta4 in Solaris 7, it crashes just after a connection is established. Nothing appears in the stunnel log. If I run it in foreground mode, "Bus Error" appears on the console. Running with 'truss -f', I see the output that follows. Gdb reveals nothing (it's not compiled for debug and I"m not sure how to change that). so_socket(2, 2, 0, "", 1) = 9 fcntl(9, F_GETFL, 0x00000000) = 2 fstat64(9, 0x001686B8) = 0 getsockopt(9, 65535, 8192, 0x001687B8, 0x001687B0, 0) = 0 fstat64(9, 0x001686B8) = 0 getsockopt(9, 65535, 8192, 0x001687B8, 0x001687B4, 0) = 0 setsockopt(9, 65535, 8192, 0x001687B8, 4, 0) = 0 fcntl(9, F_SETFL, 0x00000082) = 0 time() = 1118632479 getpid() = 25472 [25471] write(3, " 2 0 0 5 . 0 6 . 1 3 1".., 61) = 61 time() = 1118632479 getpid() = 25472 [25471] write(3, " 2 0 0 5 . 0 6 . 1 3 1".., 78) = 78 connect(9, 0x00168998, 16, 1) = 0 time() = 1118632479 getpid() = 25472 [25471] write(3, " 2 0 0 5 . 0 6 . 1 3 1".., 59) = 59 Incurred fault #5, FLTACCESS %pc = 0x00031720 siginfo: SIGBUS BUS_ADRALN addr=0x0002CDE9 Received signal #10, SIGBUS [default] siginfo: SIGBUS BUS_ADRALN addr=0x0002CDE9 *** process killed *** The stunnel options are: stunnel 4.10 on sparc-sun-solaris2.7 UCONTEXT+POLL+IPv4 with OpenSSL 0.9.8-beta4 06 Jun 2005 Global options cert = /u/etc/stunnel/stunnel.pem ciphers = ALL:!ADH:+RC4:@STRENGTH debug = 5 key = /u/etc/stunnel/stunnel.pem pid = /u/var/run/stunnel.pid RNDbytes = 64 RNDoverwrite = yes session = 300 seconds verify = none Service-level options TIMEOUTbusy = 300 seconds TIMEOUTclose = 60 seconds TIMEOUTconnect = 10 seconds TIMEOUTidle = 43200 seconds Also, I had some warnings errors during compilation , which should be fixed (compiling with gcc 3.4.1 in pedantic mode). (None of them are the cause of the crash though, as I hacked up some fixes and the crash still happened). log.c: In function `s_log': log.c:134: warning: implicit declaration of function `localtime_r' log.c:134: warning: assignment makes pointer from integer without a cast The culprit here is that config.h defines HAVE_LOCALTIME_R, but when the system header with that function is included, the #defines are set up so that localtime_r is NOT defined. (I guess this is an autoconf problem). The code links successfully but I'm not sure how reliable it will be, since localtime_r was not declared properly. options.c and network: there were many uses of isspace() with a (signed) char value, this is incorrect (isspace requires an unsigned char value -- it could fail if it gets a negative number). However many C libraries (eg. glibc) work with negative values anyway, although I have used compilers that don't. resolver.c has some cases of potential alignment errors, but I guess they aren't a problem in this case.

1 0

Compile stunnel 4.10 using VC7(aka Visual Studio 2003)
by Han Jun Li 23 Jun '05

23 Jun '05

Stunnel 4.10 does not compile with Visual Studio 7. After spending the past few days to get it to compile, I thought someone might find this useful. There is a change to the common.h that you need to hack. Basically, you need to include <winsock2.h> and <ws2tcpip.h> before <windows.h> to make it compile without any warning. The content of the make file(stunnel.mak) is below: !IF "$(CFG)" == "" CFG=stunnel - Release !MESSAGE No configuration specified. Defaulting to "stunnel - Release" !ENDIF !IF "$(CFG)" != "stunnel - Release" !MESSAGE Invalid configuration "$(CFG)" specified. !MESSAGE You can specify a configuration when running NMAKE !MESSAGE by defining the macro CFG on the command line. For example: !MESSAGE !MESSAGE NMAKE /f "stunnel.mak" CFG="stunnel - Release" !MESSAGE !MESSAGE Possible choices for configuration are: !MESSAGE !MESSAGE "stunnel Release" (based on "Win32 (x86) Console Application") !MESSAGE !ERROR An invalid configuration is specified. !ENDIF !IF "$(OS)" == "Windows_NT" NULL= !ELSE NULL=nul !ENDIF CPP=cl.exe RSC=rc.exe !IF "$(CFG)" == "stunnel - Release" OPENSSL=c:\openssl-0.9.7g !MESSAGE === OpenSSL is configured to be at $(OPENSSL) === OUTDIR=.\Release INTDIR=.\Release # Begin Custom Macros OutDir=.\Release # End Custom Macros ALL : "$(OUTDIR)\stunnel.exe" CLEAN : -@erase "$(INTDIR)\client.obj" -@erase "$(INTDIR)\gui.obj" -@erase "$(INTDIR)\log.obj" -@erase "$(INTDIR)\network.obj" -@erase "$(INTDIR)\options.obj" -@erase "$(INTDIR)\protocol.obj" -@erase "$(INTDIR)\resources.res" -@erase "$(INTDIR)\resolver.obj" -@erase "$(INTDIR)\ssl.obj" -@erase "$(INTDIR)\sthreads.obj" -@erase "$(INTDIR)\stunnel.obj" -@erase "$(INTDIR)\vc60.idb" -@erase "$(OUTDIR)\stunnel.exe" "$(OUTDIR)" : if not exist "$(OUTDIR)/$(NULL)" mkdir "$(OUTDIR)" CPP_PROJ=/nologo /MT /W3 /G5 /O2 /I "$(OPENSSL)\inc32" /D "WIN32" /D "NDEBUG" /D "_WINDOWS" /D "_MBCS" /D "USE_WIN32" /D "HAVE_OPENSSL" /D "HAVE_GETADDRINFO" /D "HAVE_GETNAMEINFO" /Fo"$(INTDIR)\\" /Fd"$(INTDIR)\\" /FD /c RSC_PROJ=/l 0x409 /fo"$(INTDIR)\resources.res" /d "NDEBUG" .c{$(INTDIR)}.obj:: $(CPP) @<< $(CPP_PROJ) $< << .cpp{$(INTDIR)}.obj:: $(CPP) @<< $(CPP_PROJ) $< << .cxx{$(INTDIR)}.obj:: $(CPP) @<< $(CPP_PROJ) $< << .c{$(INTDIR)}.sbr:: $(CPP) @<< $(CPP_PROJ) $< << .cpp{$(INTDIR)}.sbr:: $(CPP) @<< $(CPP_PROJ) $< << .cxx{$(INTDIR)}.sbr:: $(CPP) @<< $(CPP_PROJ) $< << BSC32=bscmake.exe BSC32_FLAGS=/nologo /o"$(OUTDIR)\stunnel.bsc" BSC32_SBRS= \ LINK32=link.exe LINK32_FLAGS=kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib wsock32.lib $(OPENSSL)\out32dll\ssleay32.lib $(OPENSSL)\out32dll\libeay32.lib /nologo /subsystem:windows /incremental:no /pdb:"$(OUTDIR)\stunnel.pdb" /machine:I386 /out:"$(OUTDIR)\stunnel.exe" LINK32_OBJS= \ "$(INTDIR)\stunnel.obj" \ "$(INTDIR)\client.obj" \ "$(INTDIR)\gui.obj" \ "$(INTDIR)\log.obj" \ "$(INTDIR)\network.obj" \ "$(INTDIR)\options.obj" \ "$(INTDIR)\protocol.obj" \ "$(INTDIR)\resources.res" \ "$(INTDIR)\resolver.obj" \ "$(INTDIR)\ssl.obj" \ "$(INTDIR)\sthreads.obj" "$(OUTDIR)\stunnel.exe" : "$(OUTDIR)" $(DEF_FILE) $(LINK32_OBJS) $(LINK32) @<< $(LINK32_FLAGS) $(LINK32_OBJS) << !ENDIF !IF "$(CFG)" == "stunnel - Release" || "$(CFG)" == "stunnel - Debug" SOURCE=.\client.c "$(INTDIR)\client.obj" : $(SOURCE) "$(INTDIR)" SOURCE=.\gui.c "$(INTDIR)\gui.obj" : $(SOURCE) "$(INTDIR)" SOURCE=.\log.c "$(INTDIR)\log.obj" : $(SOURCE) "$(INTDIR)" SOURCE=.\network.c "$(INTDIR)\network.obj" : $(SOURCE) "$(INTDIR)" SOURCE=.\options.c "$(INTDIR)\options.obj" : $(SOURCE) "$(INTDIR)" SOURCE=.\protocol.c "$(INTDIR)\protocol.obj" : $(SOURCE) "$(INTDIR)" SOURCE=.\resources.rc "$(INTDIR)\resources.res" : $(SOURCE) "$(INTDIR)" $(RSC) $(RSC_PROJ) $(SOURCE) SOURCE=.\resolver.c "$(INTDIR)\resolver.obj" : $(SOURCE) "$(INTDIR)" SOURCE=.\ssl.c "$(INTDIR)\ssl.obj" : $(SOURCE) "$(INTDIR)" SOURCE=.\sthreads.c "$(INTDIR)\sthreads.obj" : $(SOURCE) "$(INTDIR)" SOURCE=.\stunnel.c "$(INTDIR)\stunnel.obj" : $(SOURCE) "$(INTDIR)" !ENDIF

1 0

Certificate integrration
by Nadeem Mohiudeen 23 Jun '05

23 Jun '05

Dear Members, I need to know the procedures to install a *.cer file into the format we using in stunnel.conf.actually lately we renewed a certificate from Verisign and they send a file which we save as test.cer .now I need to put this file into my format in stunnel.conf as follows key = /pbx_u01/apps/tomcat/current/conf/mnet-priv_nbk.pfx.pem cert = /pbx_u01/apps/tomcat/current/conf/mnet-priv_nbk.pfx.x509 since we are using tomcat as application server which is using stunnel as https port forwarder so advice the steps would be thanks at the earliest. Regards Nadeem

2 1

Help
by Nadeem Mohiudeen 23 Jun '05

23 Jun '05

Dear Members, I need to know the procedures to install a *.cer file into the format we using in stunnel.conf.actually lately we renewed a certificate from Verisign and they send a file which we save as test.cer .now I need to put this file into my format in stunnel.conf as follows key = /pbx_u01/apps/tomcat/current/conf/mnet-priv_nbk.pfx.pem cert = /pbx_u01/apps/tomcat/current/conf/mnet-priv_nbk.pfx.x509 since we are using tomcat as application server which is using stunnel as https port forwarder so advice the steps would be thanks at the earliest. Regards Nadeem

1 0

Re: [stunnel-users] Passphrase validation
by Vasil Dimov 23 Jun '05

23 Jun '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, Jun 22, 2005 at 04:30:56PM -0700, Joseph Mocker wrote: > > It depends on how the machine were broken. Presumably if you > were that hell-bent on using passprhases on private keys, you'd > likely isolate stunnel to run as an unpriviledged user in a chrooted That is a good idea anyway :) > environment, and you may very well set the coredump size to zero > and remove a debugger all together. So unless the user was able > to break root, the effects of the break-in might be minimized. Private key stealing table: * the key and the plain text file, holding the password (if any) should always be chown root and chmod 400 * stunnel is the (unprivileged) user stunnel is running as * we assume that stunnel is running at the time of breakage, because this is the worst case. key storage \ break as root stunnel other user - --------------------------------------------------------------------------- 1. unencrypted key YES YES NO 2. crypted key/password in text file YES YES NO 3. crypted key/password entered at startup YES YES NO - --------------------------------------------------------------------------- As we see there is no difference if the private key will be kept crypted or unencrypted with or without text file holding the passphrase. What happens if the stunnel daemon is not running during the breakage? Note that this is an optimistic suggestion and we should not rely on it. key storage \ break as root stunnel other user - --------------------------------------------------------------------------- 1. unencrypted key YES NO NO 2. crypted key/password in text file YES NO NO 3. crypted key/password entered at startup NO NO NO - --------------------------------------------------------------------------- So the only difference in all cases is if stunnel is not running and the hacker gets root on the machine and the key is crypted and the password is entered at startup - then it will not be possible to steal the private key. As a conclusion, it is obviously - that there is really no sense to keep the password in a text file and it makes a LITTLE sense if the password is entered at startup - in just one, rare, case this setup will save the private key. -----BEGIN PGP SIGNATURE----- iD8DBQFCunHRFw6SP/bBpCARAtN4AJ0TBfANXVyyLNKojIaFzb1E/7WBqQCeIcop rAqsbhJmK9oBYg/Rb9iJzSE= =rFAJ -----END PGP SIGNATURE-----

1 0

Re: [stunnel-users] Passphrase validation
by Vasil Dimov 23 Jun '05

23 Jun '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, Jun 22, 2005 at 01:20:10PM +0100, Colin McKinnon wrote: > On Wednesday 22 June 2005 13:12, Vasil Dimov wrote: > > On Tue, Jun 21, 2005 at 10:29:37PM -0700, Peter Pentes wrote: > > > Sorry, what I am referring to here is actually the > > > passphrase for the private keys, and how Stunnel does > > > not support encrypted private keys. > > > > This would be useless. How do you expect the passphrase for the > > encrypted private key to be obtained at stunnel startup? > > Apache manages it. > Encrypted private keys will prevent stunnel from automatic startup, after a power failure or some other accidential machine reboot. And even being crypted on the filesystem once decrypted the private key will stay in memory unencrypted all the time. If someone breaks in the machine while it is running he/she will get the key from memory not from the filesystem. The only use of crypted private keys (for deamon-services) I can think of is that you can prevent someone from stealing your private key if he/she steals physically the harddisk or the whole machine from your server-room. And even this has the major disadvantage that the service will not start without human intervention (the private key's passphrase input) after unexpected reboots. -----BEGIN PGP SIGNATURE----- iD8DBQFCuVvWFw6SP/bBpCARAuTEAJ0bdKAURvMh4VZA7QEXplNYySrxTQCgoOBH XY4ftFyPqY36xDdZww6kSFU= =2/nK -----END PGP SIGNATURE-----

2 1

Re: [stunnel-users] Passphrase validation
by Vasil Dimov 23 Jun '05

23 Jun '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, Jun 22, 2005 at 07:39:54PM +0200, Sergio Gelato wrote: > ... > operation, there is little (if any) actual security benefit from using a > non-null passphrase and storing it in a separate file; however, some > software (e.g., Java) does work that way, and I don't see any harm in ... Having encrypted private_key.pem and a plain text file private_key.pem.passphrase which contains the encryption password really does not make any sense. Ofcourse both files should be chown root and chmod 400. -----BEGIN PGP SIGNATURE----- iD8DBQFCumGtFw6SP/bBpCARAp52AJ9cOGOgwTqnuDN82ubkU5Vk3uieWgCdHQSS tBmrJ3voYiHwD9hJOwtwocM= =+cCS -----END PGP SIGNATURE-----

1 0

RE: [stunnel-users] GUI for openssl certificate generation
by Paul Jones 22 Jun '05

22 Jun '05

Hi, Yes, I do have a batch file for this purpose, though I would prefer a GUI. Could you please mail me your batch file anyway? I would like to compare. Cheers. Paul >From: "Aditya Deshmukh" <aditya.deshmukh(a)online.gateway.strangled.net> >Reply-To: <ald2003(a)users.sourceforge.net> >To: "'Paul Jones'" <jonesy_boy10(a)hotmail.com>,<stunnel-users(a)mirt.net> >Subject: RE: [stunnel-users] GUI for openssl certificate generation >Date: Wed, 22 Jun 2005 23:41:49 +0530 > >May be the best thing to do is to use a batch file for this purpose - >please >mail me if you want my batch file used for creating these certs > > > -----Original Message----- > > From: stunnel-users-bounces(a)mirt.net > > [mailto:[email protected]] On Behalf Of Paul Jones > > Sent: Wednesday, June 22, 2005 7:34 AM > > To: stunnel-users(a)mirt.net > > Subject: [stunnel-users] GUI for openssl certificate generation > > > > Hi all, > > > > I'm looking at building a small GUI app (possibly in VB6) on > > a Windows > > platform for generating certificates using OpenSSL. How can > > I do this? The > > command-line call to the openssl EXE does not seem to take > > things such as > > the Common Name, Organizational Unit, etc as parameters. > > > > Any help would be appreciated. > > > > Thanks in advance. > > > > Paul > > > > _________________________________________________________________ > > SEEK: Over 80,000 jobs across all industries at Australia's > > #1 job site. > > http://ninemsn.seek.com.au?hotmail > > > > _______________________________________________ > > stunnel-users mailing list > > stunnel-users(a)mirt.net > > http://stunnel.mirt.net/mailman/listinfo/stunnel-users > > > >________________________________________________________________________ >Delivered using the Free Personal Edition of Mailtraq (www.mailtraq.com) _________________________________________________________________ REALESTATE: biggest buy/rent/share listings http://ninemsn.realestate.com.au

1 0

Re: [stunnel-users] Passphrase validation
by Peter Pentes 22 Jun '05

22 Jun '05

I agree. It would be useful on the client side. PP --- Sergio Gelato <Sergio.Gelato(a)astro.su.se> wrote: > Vasil Dimov wrote: > > >-----BEGIN PGP SIGNED MESSAGE----- > >Hash: SHA1 > > > >On Tue, Jun 21, 2005 at 10:29:37PM -0700, Peter > Pentes wrote: > > > > > >>Sorry, what I am referring to here is actually the > >>passphrase for the private keys, and how Stunnel > does > >>not support encrypted private keys. > >> > >> > > > >This would be useless. How do you expect the > passphrase for the > >encrypted private key to be obtained at stunnel > startup? > > > > > By prompting the user, or by reading it from a > configuration file. > > On the client side, prompting the user isn't > necessarily bad or even > difficult. > > I'll grant you that on the server side, or for > unattended client-side > operation, there is little (if any) actual security > benefit from using a > non-null passphrase and storing it in a separate > file; however, some > software (e.g., Java) does work that way, and I > don't see any harm in > having that possibility. There may also be some > non-security benefits: > I've seen at least one CA policy that requires > private keys to be stored > encrypted while not active, and if you want to > comply with the letter > of such a policy you may have to use a non-null > passphrase. > ____________________________________________________ Yahoo! Sports Rekindle the Rivalries. Sign up for Fantasy Football http://football.fantasysports.yahoo.com

1 0

GUI for openssl certificate generation
by Paul Jones 22 Jun '05

22 Jun '05

Hi all, I'm looking at building a small GUI app (possibly in VB6) on a Windows platform for generating certificates using OpenSSL. How can I do this? The command-line call to the openssl EXE does not seem to take things such as the Common Name, Organizational Unit, etc as parameters. Any help would be appreciated. Thanks in advance. Paul _________________________________________________________________ SEEK: Over 80,000 jobs across all industries at Australia's #1 job site. http://ninemsn.seek.com.au?hotmail

1 1

a suggestion for release announcement
by Lu Wei 22 Jun '05

22 Jun '05

Hello Michal, thank you for your excellent software! I have a little suggestion: Could you include release files' MD5 and SHA hash codes or your pgp signature in the release announcement? That should be more reliable, should it? -- Regards Lu Wei

1 0

Stunnel for QNX4
by hazael martinez 21 Jun '05

21 Jun '05

Hi, Does anybody know if stunnel would work under QNX4? Or has anybody seen a port to QNX4? I downloaded the sources but I haven't been able to compile them. Thank you ____________________________________________________ Yahoo! Sports Rekindle the Rivalries. Sign up for Fantasy Football http://football.fantasysports.yahoo.com

1 0

Stunnel crashing
by David Gomel 21 Jun '05

21 Jun '05

I have been having some major problems trying to secure pop3 and imap with stunnel. I am running a RHEL3 box with Cpanel. I first started off by installing a clean copy of stunnel 4.10 but it was causing numerous bizarre problems. 1) it would crash after a few hours of the daemon operating, 2) before it would crash I would be getting tons of 'mailbox locked' errors and 3) the occasional timeout connecting. I eventually gave up with 4.10 and decided to try to use the stunnel 4.04 that was already doing https for cpanel/whm. I created a separate config file and ran a separate daemon just for pop/imap (I did this because I want them to be using different SSL certs). This seemed to be working perfectly as there were no timeouts, no locked mailbox errors and it didn't seem to be crashing. After about 24 hours however, the process had shut down. I tried a few more times and again after about 12-24 hours of running my pop/imap only stunnel daemon crashes. I should also mention 2 other things: 1) prior to having set up 4.10 on my box, stunnel 4.04 was listening for pop/imap without crashing (it just wasn't being used however). 2) The other daemon running https for cpanel/whm hasn't crashed at all. I've included the log (level 7) for everything that happened in the 1-2 seconds before it crashed. If anyone could offer any advice, it would be greatly appreciated! Thanks! David Info needed: 1) Running stunnel by executing "/usr/bin/stunnel-4.04local /usr/local/cpanel/etc/stunnel/my/stunnel2.conf" 2) Output of "stunnel -version": stunnel 4.04 on i386-redhat-linux-gnu PTHREAD+LIBWRAP with OpenSSL 0.9.7a Feb 19 2003 Global options cert = /etc/stunnel/stunnel.pem ciphers = ALL:!ADH:+RC4:@STRENGTH debug = 5 key = /etc/stunnel/stunnel.pem pid = /var/run/stunnel.pid RNDbytes = 64 RNDfile = /dev/urandom RNDoverwrite = yes session = 300 seconds verify = none Service-level options TIMEOUTbusy = 300 seconds TIMEOUTclose = 60 seconds TIMEOUTidle = 43200 seconds 3) Output of "uname -a": Linux MY.HOSTNAME.COM 2.4.21-15.0.3.EL #1 Tue Jun 29 18:17:52 EDT 2004 i686 i686 i386 GNU/Linux 4) Your libc version: Version 6 5) Output of "gcc -v": Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-52) 6) Output of "openssl version": OpenSSL 0.9.7a Feb 19 2003 7) Log before crash: 2005.06.19 05:10:30 LOG7[7052:3209298656]: pop3s accepted FD=8 from 82.123.194.23:63627 2005.06.19 05:10:30 LOG7[7052:3209298656]: FD 8 in non-blocking mode 2005.06.19 05:10:30 LOG7[7052:3200814000]: pop3s started 2005.06.19 05:10:30 LOG5[7052:3200814000]: pop3s connected from 82.123.194.23:63627 2005.06.19 05:10:30 LOG7[7052:3200814000]: SSL state (accept): before/accept initialization 2005.06.19 05:10:30 LOG7[7052:3200814000]: waitforsocket: FD=8, DIR=read 2005.06.19 05:10:30 LOG7[7052:3200814000]: waitforsocket: ok 2005.06.19 05:10:30 LOG7[7052:3200814000]: SSL state (accept): SSLv3 read client hello A 2005.06.19 05:10:30 LOG7[7052:3200814000]: SSL state (accept): SSLv3 write server hello A 2005.06.19 05:10:30 LOG7[7052:3200814000]: SSL state (accept): SSLv3 write certificate A 2005.06.19 05:10:30 LOG7[7052:3200814000]: SSL state (accept): SSLv3 write server done A 2005.06.19 05:10:30 LOG7[7052:3200814000]: SSL state (accept): SSLv3 flush data 2005.06.19 05:10:30 LOG7[7052:3200814000]: waitforsocket: FD=8, DIR=read 2005.06.19 05:10:30 LOG7[7052:3209298656]: pop3s accepted FD=9 from 82.123.194.23:63628 2005.06.19 05:10:30 LOG7[7052:3209298656]: FD 9 in non-blocking mode 2005.06.19 05:10:30 LOG7[7052:3209206704]: pop3s started 2005.06.19 05:10:30 LOG5[7052:3209206704]: pop3s connected from 82.123.194.23:63628 2005.06.19 05:10:30 LOG7[7052:3209206704]: SSL state (accept): before/accept initialization 2005.06.19 05:10:30 LOG7[7052:3209206704]: waitforsocket: FD=9, DIR=read 2005.06.19 05:10:30 LOG7[7052:3200814000]: waitforsocket: ok 2005.06.19 05:10:30 LOG7[7052:3200814000]: SSL state (accept): SSLv3 read client key exchange A 2005.06.19 05:10:30 LOG7[7052:3200814000]: waitforsocket: FD=8, DIR=read 2005.06.19 05:10:30 LOG7[7052:3209206704]: waitforsocket: ok 2005.06.19 05:10:30 LOG7[7052:3209206704]: SSL state (accept): SSLv3 read client hello A 2005.06.19 05:10:30 LOG7[7052:3209206704]: SSL state (accept): SSLv3 write server hello A 2005.06.19 05:10:30 LOG7[7052:3209206704]: SSL state (accept): SSLv3 write certificate A 2005.06.19 05:10:30 LOG7[7052:3209206704]: SSL state (accept): SSLv3 write server done A 2005.06.19 05:10:30 LOG7[7052:3209206704]: SSL state (accept): SSLv3 flush data 2005.06.19 05:10:30 LOG7[7052:3209206704]: waitforsocket: FD=9, DIR=read 2005.06.19 05:10:30 LOG7[7052:3200814000]: waitforsocket: ok 2005.06.19 05:10:30 LOG7[7052:3200814000]: waitforsocket: FD=8, DIR=read 2005.06.19 05:10:30 LOG7[7052:3209206704]: waitforsocket: ok 2005.06.19 05:10:30 LOG7[7052:3209206704]: SSL state (accept): SSLv3 read client key exchange A 2005.06.19 05:10:30 LOG7[7052:3209206704]: waitforsocket: FD=9, DIR=read 2005.06.19 05:10:30 LOG7[7052:3200814000]: waitforsocket: ok 2005.06.19 05:10:30 LOG7[7052:3200814000]: SSL state (accept): SSLv3 read finished A 2005.06.19 05:10:30 LOG7[7052:3200814000]: SSL state (accept): SSLv3 write change cipher spec A 2005.06.19 05:10:30 LOG7[7052:3200814000]: SSL state (accept): SSLv3 write finished A 2005.06.19 05:10:30 LOG7[7052:3200814000]: SSL state (accept): SSLv3 flush data 2005.06.19 05:10:30 LOG7[7052:3200814000]: 113 items in the session cache 2005.06.19 05:10:30 LOG7[7052:3200814000]: 0 client connects (SSL_connect()) 2005.06.19 05:10:30 LOG7[7052:3200814000]: 0 client connects that finished 2005.06.19 05:10:30 LOG7[7052:3200814000]: 0 client renegotiatations requested 2005.06.19 05:10:30 LOG7[7052:3200814000]: 622 server connects (SSL_accept()) 2005.06.19 05:10:30 LOG7[7052:3200814000]: 621 server connects that finished 2005.06.19 05:10:30 LOG7[7052:3200814000]: 0 server renegotiatiations requested 2005.06.19 05:10:30 LOG7[7052:3200814000]: 0 session cache hits 2005.06.19 05:10:30 LOG7[7052:3200814000]: 0 session cache misses 2005.06.19 05:10:30 LOG7[7052:3200814000]: 0 session cache timeouts 2005.06.19 05:10:30 LOG6[7052:3200814000]: Negotiated ciphers: DES-CBC3-SHA SSLv3 Kx=RSA Au=RSA Enc=3DES(168) Mac=SHA1 2005.06.19 05:10:30 LOG7[7052:3200814000]: FD 10 in non-blocking mode 2005.06.19 05:10:30 LOG7[7052:3200814000]: pop3s connecting 127.0.0.1:110 2005.06.19 05:10:30 LOG7[7052:3200814000]: remote connect #1: EINPROGRESS: retrying 2005.06.19 05:10:30 LOG7[7052:3200814000]: waitforsocket: FD=10, DIR=write 2005.06.19 05:10:30 LOG7[7052:3200814000]: waitforsocket: ok 2005.06.19 05:10:30 LOG7[7052:3200814000]: Remote FD=10 initialized 2005.06.19 05:10:30 LOG7[7052:3209298656]: pop3s accepted FD=11 from 82.123.194.23:63631 2005.06.19 05:10:30 LOG7[7052:3209298656]: FD 11 in non-blocking mode 2005.06.19 05:10:30 LOG7[7052:3192421296]: pop3s started 2005.06.19 05:10:30 LOG5[7052:3192421296]: pop3s connected from 82.123.194.23:63631 2005.06.19 05:10:30 LOG7[7052:3192421296]: SSL state (accept): before/accept initialization 2005.06.19 05:10:30 LOG7[7052:3192421296]: waitforsocket: FD=11, DIR=read 2005.06.19 05:10:31 LOG7[7052:3192421296]: waitforsocket: ok 2005.06.19 05:10:31 LOG7[7052:3192421296]: SSL state (accept): SSLv3 read client hello A 2005.06.19 05:10:31 LOG7[7052:3192421296]: SSL state (accept): SSLv3 write server hello A 2005.06.19 05:10:31 LOG7[7052:3192421296]: SSL state (accept): SSLv3 write certificate A 2005.06.19 05:10:31 LOG7[7052:3192421296]: SSL state (accept): SSLv3 write server done A 2005.06.19 05:10:31 LOG7[7052:3192421296]: SSL state (accept): SSLv3 flush data 2005.06.19 05:10:31 LOG7[7052:3192421296]: waitforsocket: FD=11, DIR=read 2005.06.19 05:10:31 LOG7[7052:3209206704]: waitforsocket: ok 2005.06.19 05:10:31 LOG7[7052:3209206704]: waitforsocket: FD=9, DIR=read 2005.06.19 05:10:31 LOG7[7052:3209298656]: pop3s accepted FD=12 from 82.123.194.23:63632 2005.06.19 05:10:31 LOG7[7052:3209298656]: FD 12 in non-blocking mode 2005.06.19 05:10:31 LOG7[7052:3184028592]: pop3s started 2005.06.19 05:10:31 LOG5[7052:3184028592]: pop3s connected from 82.123.194.23:63632 2005.06.19 05:10:31 LOG7[7052:3184028592]: SSL state (accept): before/accept initialization 2005.06.19 05:10:31 LOG7[7052:3184028592]: waitforsocket: FD=12, DIR=read 2005.06.19 05:10:31 LOG7[7052:3209206704]: waitforsocket: ok 2005.06.19 05:10:31 LOG7[7052:3209206704]: SSL state (accept): SSLv3 read finished A 2005.06.19 05:10:31 LOG7[7052:3209206704]: SSL state (accept): SSLv3 write change cipher spec A 2005.06.19 05:10:31 LOG7[7052:3209206704]: SSL state (accept): SSLv3 write finished A 2005.06.19 05:10:31 LOG7[7052:3209206704]: SSL state (accept): SSLv3 flush data 2005.06.19 05:10:31 LOG7[7052:3209206704]: 114 items in the session cache 2005.06.19 05:10:31 LOG7[7052:3209206704]: 0 client connects (SSL_connect()) 2005.06.19 05:10:31 LOG7[7052:3209206704]: 0 client connects that finished 2005.06.19 05:10:31 LOG7[7052:3209206704]: 0 client renegotiatations requested 2005.06.19 05:10:31 LOG7[7052:3209206704]: 624 server connects (SSL_accept()) 2005.06.19 05:10:31 LOG7[7052:3209206704]: 622 server connects that finished 2005.06.19 05:10:31 LOG7[7052:3209206704]: 0 server renegotiatiations requested 2005.06.19 05:10:31 LOG7[7052:3209206704]: 0 session cache hits 2005.06.19 05:10:31 LOG7[7052:3209206704]: 0 session cache misses 2005.06.19 05:10:31 LOG7[7052:3209206704]: 0 session cache timeouts 2005.06.19 05:10:31 LOG6[7052:3209206704]: Negotiated ciphers: DES-CBC3-SHA SSLv3 Kx=RSA Au=RSA Enc=3DES(168) Mac=SHA1 2005.06.19 05:10:31 LOG7[7052:3209206704]: FD 13 in non-blocking mode 2005.06.19 05:10:31 LOG7[7052:3209206704]: pop3s connecting 127.0.0.1:110 2005.06.19 05:10:31 LOG7[7052:3209206704]: remote connect #1: EINPROGRESS: retrying 2005.06.19 05:10:31 LOG7[7052:3209206704]: waitforsocket: FD=13, DIR=write 2005.06.19 05:10:31 LOG7[7052:3209206704]: waitforsocket: ok 2005.06.19 05:10:31 LOG7[7052:3209206704]: Remote FD=13 initialized 2005.06.19 05:10:31 LOG7[7052:3192421296]: waitforsocket: ok 2005.06.19 05:10:31 LOG7[7052:3192421296]: SSL state (accept): SSLv3 read client key exchange A 2005.06.19 05:10:31 LOG7[7052:3192421296]: waitforsocket: FD=11, DIR=read 2005.06.19 05:10:31 LOG7[7052:3184028592]: waitforsocket: ok 2005.06.19 05:10:31 LOG7[7052:3184028592]: SSL state (accept): SSLv3 read client hello A 2005.06.19 05:10:31 LOG7[7052:3184028592]: SSL state (accept): SSLv3 write server hello A 2005.06.19 05:10:31 LOG7[7052:3184028592]: SSL state (accept): SSLv3 write certificate A 2005.06.19 05:10:31 LOG7[7052:3184028592]: SSL state (accept): SSLv3 write server done A 2005.06.19 05:10:31 LOG7[7052:3184028592]: SSL state (accept): SSLv3 flush data 2005.06.19 05:10:31 LOG7[7052:3184028592]: waitforsocket: FD=12, DIR=read 2005.06.19 05:10:31 LOG7[7052:3192421296]: waitforsocket: ok 2005.06.19 05:10:31 LOG7[7052:3192421296]: SSL state (accept): SSLv3 read finished A 2005.06.19 05:10:31 LOG7[7052:3192421296]: SSL state (accept): SSLv3 write change cipher spec A 2005.06.19 05:10:31 LOG7[7052:3192421296]: SSL state (accept): SSLv3 write finished A 2005.06.19 05:10:31 LOG7[7052:3192421296]: SSL state (accept): SSLv3 flush data 2005.06.19 05:10:31 LOG7[7052:3192421296]: 115 items in the session cache 2005.06.19 05:10:31 LOG7[7052:3192421296]: 0 client connects (SSL_connect()) 2005.06.19 05:10:31 LOG7[7052:3192421296]: 0 client connects that finished 2005.06.19 05:10:31 LOG7[7052:3192421296]: 0 client renegotiatations requested 2005.06.19 05:10:31 LOG7[7052:3192421296]: 624 server connects (SSL_accept()) 2005.06.19 05:10:31 LOG7[7052:3192421296]: 623 server connects that finished 2005.06.19 05:10:31 LOG7[7052:3192421296]: 0 server renegotiatiations requested 2005.06.19 05:10:31 LOG7[7052:3192421296]: 0 session cache hits 2005.06.19 05:10:31 LOG7[7052:3192421296]: 0 session cache misses 2005.06.19 05:10:31 LOG7[7052:3192421296]: 0 session cache timeouts 2005.06.19 05:10:31 LOG6[7052:3192421296]: Negotiated ciphers: DES-CBC3-SHA SSLv3 Kx=RSA Au=RSA Enc=3DES(168) Mac=SHA1 2005.06.19 05:10:31 LOG7[7052:3192421296]: FD 14 in non-blocking mode 2005.06.19 05:10:31 LOG7[7052:3192421296]: pop3s connecting 127.0.0.1:110 2005.06.19 05:10:31 LOG7[7052:3192421296]: remote connect #1: EINPROGRESS: retrying 2005.06.19 05:10:31 LOG7[7052:3192421296]: waitforsocket: FD=14, DIR=write 2005.06.19 05:10:31 LOG7[7052:3192421296]: waitforsocket: ok 2005.06.19 05:10:31 LOG7[7052:3192421296]: Remote FD=14 initialized 2005.06.19 05:10:31 LOG7[7052:3184028592]: waitforsocket: ok 2005.06.19 05:10:31 LOG7[7052:3184028592]: SSL state (accept): SSLv3 read client key exchange A 2005.06.19 05:10:31 LOG7[7052:3184028592]: waitforsocket: FD=12, DIR=read 2005.06.19 05:10:31 LOG7[7052:3184028592]: waitforsocket: ok 2005.06.19 05:10:31 LOG7[7052:3184028592]: SSL state (accept): SSLv3 read finished A 2005.06.19 05:10:31 LOG7[7052:3184028592]: SSL state (accept): SSLv3 write change cipher spec A 2005.06.19 05:10:31 LOG7[7052:3184028592]: SSL state (accept): SSLv3 write finished A 2005.06.19 05:10:31 LOG7[7052:3184028592]: SSL state (accept): SSLv3 flush data 2005.06.19 05:10:31 LOG7[7052:3184028592]: 116 items in the session cache 2005.06.19 05:10:31 LOG7[7052:3184028592]: 0 client connects (SSL_connect()) 2005.06.19 05:10:31 LOG7[7052:3184028592]: 0 client connects that finished 2005.06.19 05:10:31 LOG7[7052:3184028592]: 0 client renegotiatations requested 2005.06.19 05:10:31 LOG7[7052:3184028592]: 624 server connects (SSL_accept()) 2005.06.19 05:10:31 LOG7[7052:3184028592]: 624 server connects that finished 2005.06.19 05:10:31 LOG7[7052:3184028592]: 0 server renegotiatiations requested 2005.06.19 05:10:31 LOG7[7052:3184028592]: 0 session cache hits 2005.06.19 05:10:31 LOG7[7052:3184028592]: 0 session cache misses 2005.06.19 05:10:31 LOG7[7052:3184028592]: 0 session cache timeouts 2005.06.19 05:10:31 LOG6[7052:3184028592]: Negotiated ciphers: DES-CBC3-SHA SSLv3 Kx=RSA Au=RSA Enc=3DES(168) Mac=SHA1 2005.06.19 05:10:31 LOG7[7052:3184028592]: FD 15 in non-blocking mode 2005.06.19 05:10:31 LOG7[7052:3184028592]: pop3s connecting 127.0.0.1:110 2005.06.19 05:10:31 LOG7[7052:3184028592]: remote connect #1: EINPROGRESS: retrying 2005.06.19 05:10:31 LOG7[7052:3184028592]: waitforsocket: FD=15, DIR=write 2005.06.19 05:10:31 LOG7[7052:3184028592]: waitforsocket: ok 2005.06.19 05:10:31 LOG7[7052:3184028592]: Remote FD=15 initialized 2005.06.19 05:10:33 LOG7[7052:3200814000]: Socket closed on read 2005.06.19 05:10:33 LOG7[7052:3200814000]: SSL alert (write): warning: close notify 2005.06.19 05:10:33 LOG7[7052:3200814000]: SSL write shutdown (output buffer empty) 2005.06.19 05:10:34 LOG7[7052:3209206704]: Socket closed on read 2005.06.19 05:10:34 LOG7[7052:3209206704]: SSL alert (write): warning: close notify 2005.06.19 05:10:34 LOG7[7052:3209206704]: SSL write shutdown (output buffer empty) 2005.06.19 05:10:34 LOG7[7052:3192421296]: Socket closed on read 2005.06.19 05:10:34 LOG7[7052:3192421296]: SSL alert (write): warning: close notify 2005.06.19 05:10:34 LOG7[7052:3192421296]: SSL write shutdown (output buffer empty) 2005.06.19 05:10:34 LOG7[7052:3200814000]: SSL socket closed on SSL_read 2005.06.19 05:10:34 LOG5[7052:3200814000]: Connection closed: 3470 bytes sent to SSL, 42 bytes sent to socket 2005.06.19 05:10:34 LOG7[7052:3200814000]: pop3s finished (3 left) 2005.06.19 05:10:34 LOG7[7052:3209206704]: SSL socket closed on SSL_read 2005.06.19 05:10:34 LOG5[7052:3209206704]: Connection closed: 3342 bytes sent to SSL, 53 bytes sent to socket 2005.06.19 05:10:34 LOG7[7052:3209206704]: pop3s finished (2 left) 2005.06.19 05:10:34 LOG7[7052:3192421296]: SSL socket closed on SSL_read 2005.06.19 05:10:34 LOG5[7052:3192421296]: Connection closed: 480 bytes sent to SSL, 47 bytes sent to socket 2005.06.19 05:10:34 LOG7[7052:3192421296]: pop3s finished (1 left) 2005.06.19 05:10:34 LOG7[7052:3184028592]: Socket closed on read 2005.06.19 05:10:34 LOG7[7052:3184028592]: SSL alert (write): warning: close notify 2005.06.19 05:10:34 LOG7[7052:3184028592]: SSL write shutdown (output buffer empty) 2005.06.19 05:10:34 LOG7[7052:3184028592]: SSL socket closed on SSL_read 2005.06.19 05:10:34 LOG5[7052:3184028592]: Connection closed: 1934 bytes sent to SSL, 51 bytes sent to socket 2005.06.19 05:10:34 LOG7[7052:3184028592]: pop3s finished (0 left)

2 3

Re: [stunnel-users] stunnel 4.10 on Suse 8.2
by Ionut Turturica 18 Jun '05

18 Jun '05

I use stunnel for testing and compare results with our products. I made a script to monitor the number of threads and memory per process, now it always show 1 thread. On Fri, 17 Jun 2005 23:55:57 +0300, Michal Trojnara <Michal.Trojnara(a)mirt.net> wrote: >> Now it's ok, but I want the pthreads back :) > > Why? > > Mike -- Using Opera's revolutionary e-mail client: http://www.opera.com/m2/

2 1

Re: [stunnel-users] stunnel 4.10 on Suse 8.2
by Ionut Turturica 17 Jun '05

17 Jun '05

eh..I've missed that, it looks like a workaroud. Now it's ok, but I want the pthreads back :) On Fri, 17 Jun 2005 22:02:05 +0300, Michal Trojnara <Michal.Trojnara(a)mirt.net> wrote: > Did you try this one: > http://stunnel.mirt.net/pipermail/stunnel-users/2005-June/000532.html > ? > > Best regards, > Mike

1 0

stunnel 4.10 on Suse 8.2
by Ionut Turturica 17 Jun '05

17 Jun '05

I get a segmentation fault on first connect. To the default config, i've added the debug = 7 and foreground = yes. I have used for comparison 2 versions 4.09 and 4.10 compiled with default options (./configure, make, make install) It seems like UCONTEXT is not welcome on my machine. linux:~ # uname -a Linux linux 2.4.20-4GB #1 Mon Mar 17 17:54:44 UTC 2003 i686 unknown unknown GNU/Linux linux:~ # gcc -v Reading specs from /usr/lib/gcc-lib/i486-suse-linux/3.3/specs Configured with: ../configure --enable-threads=posix --prefix=/usr --with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib --enable-languages=c,c++,f77,objc,java,ada --disable-checking --enable-libgcj --with-gxx-include-dir=/usr/include/g++ --with-slibdir=/lib --with-system-zlib --enable-shared --enable-__cxa_atexit i486-suse-linux Thread model: posix gcc version 3.3 20030226 (prerelease) (SuSE Linux) linux:~ # openssl version OpenSSL 0.9.7g 11 Apr 2005 linux:/usr/src/stunnel-4.10 # /usr/local/sbin/stunnel 2005.06.17 11:44:17 LOG5[10371:1]: stunnel 4.10 on i686-pc-linux-gnu UCONTEXT+POLL+IPv4+LIBWRAP with OpenSSL 0.9.7g 11 Apr 2005 2005.06.17 11:44:17 LOG7[10371:1]: RAND_status claims sufficient entropy for the PRNG 2005.06.17 11:44:17 LOG6[10371:1]: PRNG seeded successfully 2005.06.17 11:44:17 LOG7[10371:1]: Certificate: /usr/local/etc/stunnel/server.pem 2005.06.17 11:44:17 LOG7[10371:1]: Key file: /usr/local/etc/stunnel/server.pem 2005.06.17 11:44:17 LOG6[10371:1]: file ulimit = 1024 (can be changed with 'ulimit -n') 2005.06.17 11:44:17 LOG6[10371:1]: poll() used - no FD_SETSIZE limit for file descriptors 2005.06.17 11:44:17 LOG5[10371:1]: 500 clients allowed 2005.06.17 11:44:17 LOG7[10371:1]: FD 3 in non-blocking mode 2005.06.17 11:44:17 LOG7[10371:1]: FD 4 in non-blocking mode 2005.06.17 11:44:17 LOG7[10371:1]: FD 5 in non-blocking mode 2005.06.17 11:44:17 LOG7[10371:1]: SO_REUSEADDR option set on accept socket 2005.06.17 11:44:17 LOG7[10371:1]: pop3s bound to 0.0.0.0:995 2005.06.17 11:44:17 LOG7[10371:1]: FD 6 in non-blocking mode 2005.06.17 11:44:18 LOG7[10371:1]: SO_REUSEADDR option set on accept socket 2005.06.17 11:44:18 LOG7[10371:1]: https bound to 0.0.0.0:443 2005.06.17 11:44:18 LOG7[10371:1]: Created pid file /stunnel.pid 2005.06.17 11:44:18 LOG7[10371:0]: Waiting -1 second(s) for 3 file descriptor(s) 2005.06.17 11:44:20 LOG7[10371:0]: CONTEXT 1, FD=3, (IN)->() 2005.06.17 11:44:20 LOG7[10371:0]: CONTEXT 1, FD=5, (IN)->(IN) 2005.06.17 11:44:20 LOG7[10371:0]: CONTEXT 1, FD=6, (IN)->() 2005.06.17 11:44:20 LOG7[10371:1]: pop3s accepted FD=7 from 172.16.203.52:2148 2005.06.17 11:44:20 LOG7[10371:1]: Creating a new context 2005.06.17 11:44:20 LOG7[10371:1]: Context 2 created Segmentation fault linux:/usr/src/stunnel-4.09 # /usr/local/sbin/stunnel 2005.06.17 11:45:13 LOG5[10773:16384]: stunnel 4.09 on i686-pc-linux-gnu PTHREAD+POLL+IPv4+LIBWRAP with OpenSSL 0.9.7g 11 Apr 2005 2005.06.17 11:45:13 LOG7[10773:16384]: RAND_status claims sufficient entropy for the PRNG 2005.06.17 11:45:13 LOG6[10773:16384]: PRNG seeded successfully 2005.06.17 11:45:13 LOG7[10773:16384]: Certificate: /usr/local/etc/stunnel/server.pem 2005.06.17 11:45:13 LOG7[10773:16384]: Key file: /usr/local/etc/stunnel/server.pem 2005.06.17 11:45:13 LOG6[10773:16384]: file ulimit = 1024 (can be changed with 'ulimit -n') 2005.06.17 11:45:13 LOG6[10773:16384]: poll() used - no FD_SETSIZE limit for file descriptors 2005.06.17 11:45:13 LOG5[10773:16384]: 500 clients allowed 2005.06.17 11:45:13 LOG7[10773:16384]: FD 3 in non-blocking mode 2005.06.17 11:45:13 LOG7[10773:16384]: FD 4 in non-blocking mode 2005.06.17 11:45:13 LOG7[10773:16384]: FD 5 in non-blocking mode 2005.06.17 11:45:13 LOG7[10773:16384]: SO_REUSEADDR option set on accept socket 2005.06.17 11:45:13 LOG7[10773:16384]: pop3s bound to 0.0.0.0:995 2005.06.17 11:45:13 LOG7[10773:16384]: FD 6 in non-blocking mode 2005.06.17 11:45:13 LOG7[10773:16384]: SO_REUSEADDR option set on accept socket 2005.06.17 11:45:13 LOG7[10773:16384]: https bound to 0.0.0.0:443 2005.06.17 11:45:13 LOG7[10773:16384]: Created pid file /stunnel.pid 2005.06.17 11:45:15 LOG7[10773:16384]: pop3s accepted FD=7 from 172.16.203.52:2150 2005.06.17 11:45:15 LOG7[10773:16384]: FD 7 in non-blocking mode 2005.06.17 11:45:15 LOG7[10779:16386]: pop3s started 2005.06.17 11:45:15 LOG7[10779:16386]: TCP_NODELAY option set on local socket 2005.06.17 11:45:15 LOG5[10779:16386]: pop3s connected from 172.16.203.52:2150 2005.06.17 11:45:15 LOG7[10779:16386]: SSL state (accept): before/accept initialization 2005.06.17 11:45:18 LOG3[10779:16386]: SSL_accept: Peer suddenly disconnected 2005.06.17 11:45:18 LOG7[10779:16386]: pop3s finished (0 left) -- Using Opera's revolutionary e-mail client: http://www.opera.com/m2/

1 0

Stunnel and Sun Calendar 5
by Michael Chanudet 17 Jun '05

17 Jun '05

Hi, I'm using stunnel with Sun Calendar on a Windows 2003 server. Everything works well until I'v move Sun Calendar on an other server. Now, when I go to my Sun Calendar, I need to refresh the page after having accepted the certificat. You can see the problem here => https://frodon.atnweb.com I'm using stunnel 4.10 libeay32.dll and libssl.dll version 0.9.7.3 (from openssl.org) My conf file looks like this: ------------------------------- key = E:\stunnel\stunnel.pem socket = l:TCP_NODELAY=1 socket = r:TCP_NODELAY=1 debug = 3 output = E:\stunnel\stunnel.log [https] accept = 443 connect = 80 TIMEOUTclose = 0 -------------------------------- If someone can see where is the problem, I will be pleased to know the answer :) Thanks, Regards, Michaël CHANUDET atn groupe sa 2 allée des Mitaillères - 38240 Meylan - France Tél. : +33 (0)4.76.41.17.17 - Fax : +33 (0)4.76.41.05.45 www.atngroupe.fr

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

stunnel-users