stunnel-users

5 participants
3315 discussions

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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

stunnel-users