- stunnel-users - stunnel.org

Can stunnel do this?
by Miguel Beccari 13 Mar '09

13 Mar '09

I tried this configuration: client = yes debug = debug cert =/Users/etc/stunnel/stunnel.pem [imaps] accept = localhost:143 delay = yes connect = remote:993 and it worked! But if I change "accept = localhost:143" to "accept = localhost:993" it does not work. I need a imaps proxy. Logs does not say anything interesting (SSL accepted: new session negotiated) Thank you all, Miguel

1 0

Newbie Question - Moving stunnel to another machine
by Dave Nasralla 13 Mar '09

13 Mar '09

Hi, I'm pretty new to the unix command line and stunnel. I am running Mac OS 10.5 with the latest version of stunnel. I was able to get stunnel up and running on my computer and it is working fine ( - I installed X-Cold, used Darwinports, got it compiled and configured, and launching at bootup). My question is: If I have an identical Machine (same hardware and OS), is there an easy way to move stunnel over to it? I copied the stunnel executable and the configuration file over to the new machine. I ran it from the terminal command line. % /Applications/stunnel /Applications/stunnel.conf The original location on my machine was (/opt/local/bin/stunnel /opt/ local/etc/stunnel/stunnel.conf) No errors (got the prompt back). But no services start on the configured ports. Am I missing support files? Or am I being dumb to think you can simply copy the program over. I was hoping to not have to jump through the same hoops to get it up and running. Any direction would be appreciated. Thanks, dave naz PS It is a simple configuration to help non SSL Mail clients connect to GMail - no certs involved.

1 0

Configuring stunnel to use p12 and p7b in client mode
by Eduard Witteveen 10 Mar '09

10 Mar '09

Hello, I'm trying to get stunnel running on my local system, so it will connect to the remote a host, which requires authentication with this p12 file(with password). I also have the chain of trust which is in the p7b file. The reason why i want to do this, is that the remote host exposes a soap interface by https, and i think it would be a good idea to tunnel the communications with stunnel, so a transparant configuration can be used. Also, this would mean there is no configuration needed for the browser anymore, since it can connect to the localhost instead of to the remoteserver. I've tested the p12(certificate PKCS12?) and (trust chain PKCS7?) files with internet explorer and firefox. They work(i can browse the remotehost), but i still have to enter the password. I've converted the p12 and p7b files into dem files with the following commands: > openssl pkcs12 -in certificate.p12 -out certificate.pem > Enter Import Password: > MAC verified OKK > Enter PEM pass phrase: > Verifying - Enter PEM pass phrase firefox: store as PEM with chain chain.p7b --> chain.pem Config: > key=certificate.pem > CAfile=chain.pem > client=yes > debug=7 > output=stunnel.log > verify=1 > [http] > accept=80 > connect=www.remoteserver.com:443 > TIMEOUTclose=0 Command: > sudo /usr/bin/stunnel4 stunnel.conf Error: > 009.03.11 00:58:10 LOG5[30424:3082909360]: Threading:PTHREAD > SSL:ENGINE > Sockets:POLL,IPv6 Auth:LIBWRAP > 2009.03.11 00:58:10 LOG6[30424:3082909360]: file ulimit = 1024 (can be > changed with 'ulimit -n') > 2009.03.11 00:58:10 LOG6[30424:3082909360]: poll() used - no > FD_SETSIZE > limit for file descriptors > 2009.03.11 00:58:10 LOG5[30424:3082909360]: 500 clients allowed > 2009.03.11 00:58:10 LOG7[30424:3082909360]: FD 10 in non-blocking mode > 2009.03.11 00:58:10 LOG7[30424:3082909360]: FD 11 in non-blocking mode > 2009.03.11 00:58:10 LOG7[30424:3082909360]: FD 12 in non-blocking mode > 2009.03.11 00:58:10 LOG7[30424:3082909360]: SO_REUSEADDR option set on > accept socket > 2009.03.11 00:58:10 LOG7[30424:3082909360]: http bound to 0.0.0.0:80 > 2009.03.11 00:58:10 LOG7[30430:3082909360]: Created pid file > /var/run/stunnel4.pid > > 2009.03.11 00:58:20 LOG7[30430:3082909360]: http accepted FD=13 from > 127.0.0.1:59793 > 2009.03.11 00:58:20 LOG7[30430:3082738576]: http started > 2009.03.11 00:58:20 LOG7[30430:3082738576]: FD 13 in non-blocking mode > 2009.03.11 00:58:20 LOG7[30430:3082738576]: Waiting for a libwrap > process > 2009.03.11 00:58:20 LOG7[30430:3082738576]: Acquired libwrap process > #0 > 2009.03.11 00:58:20 LOG7[30430:3082738576]: Releasing libwrap process > #0 > 2009.03.11 00:58:20 LOG7[30430:3082738576]: Released libwrap process > #0 > 2009.03.11 00:58:20 LOG7[30430:3082738576]: http permitted by libwrap > from > 127.0.0.1:59793 > 2009.03.11 00:58:20 LOG5[30430:3082738576]: http accepted connection > from > 127.0.0.1:59793 > 2009.03.11 00:58:20 LOG7[30430:3082738576]: FD 14 in non-blocking mode > 2009.03.11 00:58:20 LOG7[30430:3082738576]: http connecting > ${REMOTESERVER_IP}:443 > 2009.03.11 00:58:20 LOG7[30430:3082738576]: connect_wait: waiting 10 > seconds > 2009.03.11 00:58:20 LOG7[30430:3082738576]: connect_wait: connected > 2009.03.11 00:58:20 LOG5[30430:3082738576]: http connected remote > server > from 10.0.2.15:38710 > 2009.03.11 00:58:20 LOG7[30430:3082738576]: Remote FD=14 initialized > 2009.03.11 00:58:20 LOG7[30430:3082738576]: SSL state (connect): > before/connect initialization > 2009.03.11 00:58:20 LOG7[30430:3082738576]: SSL state (connect): SSLv3 > write > client hello A > 2009.03.11 00:58:20 LOG7[30430:3082738576]: SSL state (connect): SSLv3 > read > server hello A > 2009.03.11 00:58:20 LOG4[30430:3082738576]: VERIFY ERROR: depth=0, > error=unable to get local issuer certificate: ${UNIQUE NAME} > 2009.03.11 00:58:20 LOG7[30430:3082738576]: SSL alert (write): fatal: > bad > certificate > 2009.03.11 00:58:20 LOG3[30430:3082738576]: SSL_connect: 14090086: > error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate > verify > failed > 2009.03.11 00:58:20 LOG5[30430:3082738576]: Connection reset: 0 bytes > sent > to SSL, 0 bytes sent to socket > 2009.03.11 00:58:20 LOG7[30430:3082738576]: http finished (0 left) (${UNIQUE NAME} / ${REMOTESERVER_IP} were replaced) Tested by connecting the browser to http://127.0.0.1:80/ How can i get stunnel to redirect http://127.0.0.1:80/ to http://remoteserver:443/ and use the certificate and chain to validate the connection? Any pointers would also be welcome, since i searched in google but i cannot find the correct information, while one would expect that this is not the first time that this is being tried. Thanks, Eduard Witteveen

1 0

Stunnel 4.26 compile issue against openssl 0.9.8j + openssl-fips-1.2
by David W Blaine 10 Mar '09

10 Mar '09

Hi all, When I compile against OpenSSL 0.9.8j + OpenSSL-FIPS-1.2 module on Centos 4.7, I get an error in client.c: client.o(.text+0x1dd): In function `init_ssl': /tmp/stunnel-4.27/src/client.c:333: undefined reference to `FIPS_set_prng_key' collect2: ld returned 1 exit status make[1]: *** [stunnel] Error 1 make[1]: Leaving directory `/tmp/stunnel-4.27/src' make: *** [all-recursive] Error 1 It seems this call is related to a bug in OpenSSL-FIPS-1.1.1 module according to the comments. Checking the references in the includes for both OpenSSL 0.9.8j and OpenSSL-FIPS-1.2, I found that the call should be "fips_set_prng_key" with 3 arguments (the above requires only 2). So based on the comments, I removed it and I was able to successfully compile and install. Not sure if that is the right thing to do??? Dave

2 3

email through clients where no port number defined - like Outlook Express
by Richard Brust 06 Mar '09

06 Mar '09

A few days ago, sent an email in regards to a CRM program attempting to access GMail where no port number definitions are possible. That email (or part of it) is below, but after a bit more diag, I found that the email client was communicating with stunnel, but was not getting past that to GMail (or stunnel was not getting to GMail, not sure how to tell). I also realized that the settings of this application are similar to Outlook Express - email server defined, but no ability to specify port number. Does anyone have stunnel working with Outlook Express? I have a feeling the stunnel settings for that would be similar to what I need. Thanks, and the original email is below I am attempting to send/receive to GMail through a CRM program (contains email client) called ACT! (http://www.act.com) ACT! only allows server addresses in the program configuration, NOT port numbers. (e.g. smtp.gmail.com or 127.0.0.1 - nothing else) I have configured stunnel 4.26 as such: ; Some performance tunings socket = l:TCP_NODELAY=1 socket = r:TCP_NODELAY=1 ; Some debugging stuff useful for troubleshooting debug = 7 output = stunnel.log ; Use it for client mode client = yes ; Service-level configuration [pop] accept = localhost:110 connect = pop.gmail.com:995 [smtp] accept = localhost:25 connect = smtp.gmail.com:465 and in ACT as such: SMTP as localhost POP as localhost (also have tried 127.0.0.1, but with no difference). Richard Brust richard_brust(a)yahoo.com

1 0

Stunnel for tunneling all traffic (vpn)
by BS TLC 06 Mar '09

06 Mar '09

Is it possible to create 2 virtual interfaces, for tunnelling all traffic (vpn)? With ssh program it's quite simple: with the -w option 2 new (tunnel) interfaces are created (for example tun0 and tun1), and it's possible to create a vpn for all type of traffic. Best regards __________________________________________________ Do You Yahoo!? Poco spazio e tanto spam? Yahoo! Mail ti protegge dallo spam e ti da tanto spazio gratuito per i tuoi file e i messaggi http://mail.yahoo.it

2 1

stunnel with libwrap does not disconnect from terminal
by Lars Kruse 02 Mar '09

02 Mar '09

Hi, starting with v4.21, stunnel does not disconnect from the terminal anymore. This can cause problems, if the caller does not redirect stdout/stderr to /dev/null. This did not happen with v4.20. The problem disappears, when I use he "--disable-libwrap" configure switch when compiling stunnel. I am running debian testing on i386 with the stunnel4 package 4.22-2. How to reproduce: 1) stunnel config file: setuid = lars pid = /tmp/stunnel.pid [server] connect = 8080 accept = 443 cert = /some/file 2) command line: cat stunnel.conf | stunnel4 -fd 0 3) process list: erker:~/ttt/stunnel/testing/stunnel-4.26# ps -ef| grep stun lars 29599 1 0 13:47 pts/1 00:00:00 src/stunnel -fd 0 lars 29600 1 0 13:47 pts/1 00:00:00 src/stunnel -fd 0 lars 29601 1 0 13:47 pts/1 00:00:00 src/stunnel -fd 0 lars 29602 1 0 13:47 pts/1 00:00:00 src/stunnel -fd 0 lars 29603 1 0 13:47 pts/1 00:00:00 src/stunnel -fd 0 lars 29604 1 0 13:47 ? 00:00:00 src/stunnel -fd 0 4) FDs of spawned processes: erker:~/ttt/stunnel/testing/stunnel-4.26# ls -l /proc/29599/fd lrwx------ 1 root root 64 Jan 10 13:50 1 -> /dev/pts/1 lrwx------ 1 root root 64 Jan 10 13:47 2 -> /dev/pts/1 lrwx------ 1 root root 64 Jan 10 13:50 3 -> socket:[903037] Is this the expected behaviour? I use stunnel in one of my projects (http://cryptonas.org) and it started to hang with v4.22. After redirecting stdout/stderr to /dev/null, the program works again. I assume, that stunnel should take care for stdout/stderr on its own, when started in daemon mode, right? thanks for your great work! Lars

4 6

No Tray Icon in XP SP3
by Zepp 01 Mar '09

01 Mar '09

Hi all: I am running Stunnel 4.26 in Windows XP SP3. The issue I'm having is that the tray icon is missing when I install and run Stunnel as a service. the program works fine, and it shows up on the process list okay, but no tray icon appears at all. I scanned the help file and saw an option called taskbar which is supposed to be toggled on by default. I added it to the conf file anyway, and it didn't make any difference. The only way I've been able to get the icon to show is to start Stunnel by adding a shortcut to the Startup folder. Is there an option I'm missing? Thanks much! Zepp

1 0

Simple audit of configuration?
by conover＠rahul.net 01 Mar '09

01 Mar '09

Is there a simple way to verify that an stunnel configuration is secure as expected, with no configuration errors? Thanks, John -- John Conover, conover(a)rahul.net, http://www.johncon.com/

1 0

GMail on Windows using ACT
by Richard Brust 24 Feb '09

24 Feb '09

I am attempting to send/receive to GMail through a CRM program (contains email client) called ACT! (http://www.act.com) ACT! only allows server addresses in the program configuration, NOT port numbers. (e.g. smtp.gmail.com or 127.0.0.1 - nothing else) I have configured *stunnel 4.26* as such: ; Some performance tunings socket = l:TCP_NODELAY=1 socket = r:TCP_NODELAY=1 ; Some debugging stuff useful for troubleshooting debug = 7 output = stunnel.log ; Use it for client mode client = yes ; Service-level configuration [pop] accept = localhost:110 connect = pop.gmail.com:995 [smtp] accept = localhost:25 connect = smtp.gmail.com:465 and in ACT as such: SMTP as localhost POP as localhost (also have tried 127.0.0.1, but with no difference). The log is below, but the short of it is that I still cannot get through to the GMail servers. I do not see any glaring errors below, but I'm sure there is something useful. Thank you for any help... 2009.02.24 13:34:35 LOG7[3752:2216]: RAND_status claims sufficient entropy for the PRNG 2009.02.24 13:34:35 LOG7[3752:2216]: PRNG seeded successfully 2009.02.24 13:34:35 LOG7[3752:2216]: SSL context initialized for service pop 2009.02.24 13:34:35 LOG7[3752:2216]: SSL context initialized for service smtp 2009.02.24 13:34:35 LOG5[3752:2216]: stunnel 4.26 on x86-pc-mingw32-gnu with OpenSSL 0.9.8i 15 Sep 2008 2009.02.24 13:34:35 LOG5[3752:2216]: Threading:WIN32 SSL:ENGINE Sockets:SELECT,IPv6 2009.02.24 13:34:35 LOG5[3752:1576]: No limit detected for the number of clients 2009.02.24 13:34:35 LOG7[3752:1576]: FD 200 in non-blocking mode 2009.02.24 13:34:35 LOG7[3752:1576]: SO_REUSEADDR option set on accept socket 2009.02.24 13:34:35 LOG7[3752:1576]: pop bound to 127.0.0.1:110 2009.02.24 13:34:35 LOG7[3752:1576]: FD 208 in non-blocking mode 2009.02.24 13:34:35 LOG7[3752:1576]: SO_REUSEADDR option set on accept socket 2009.02.24 13:34:35 LOG7[3752:1576]: smtp bound to 127.0.0.1:25 2009.02.24 13:34:39 LOG7[3752:1576]: smtp accepted FD=216 from 127.0.0.1:3063 2009.02.24 13:34:39 LOG7[3752:1576]: Creating a new thread 2009.02.24 13:34:39 LOG7[3752:1576]: New thread created 2009.02.24 13:34:39 LOG7[3752:760]: smtp started 2009.02.24 13:34:39 LOG7[3752:760]: FD 216 in non-blocking mode 2009.02.24 13:34:39 LOG7[3752:760]: TCP_NODELAY option set on local socket 2009.02.24 13:34:39 LOG5[3752:760]: smtp accepted connection from 127.0.0.1:3063 2009.02.24 13:34:39 LOG7[3752:760]: FD 240 in non-blocking mode 2009.02.24 13:34:39 LOG7[3752:760]: smtp connecting 209.85.201.111:465 2009.02.24 13:34:39 LOG7[3752:760]: connect_wait: waiting 10 seconds 2009.02.24 13:34:39 LOG7[3752:760]: connect_wait: connected 2009.02.24 13:34:39 LOG5[3752:760]: smtp connected remote server from 192.168.1.100:3064 2009.02.24 13:34:39 LOG7[3752:760]: Remote FD=240 initialized 2009.02.24 13:34:39 LOG7[3752:760]: TCP_NODELAY option set on remote socket 2009.02.24 13:34:39 LOG7[3752:760]: SSL state (connect): before/connect initialization 2009.02.24 13:34:39 LOG7[3752:760]: SSL state (connect): SSLv3 write client hello A 2009.02.24 13:34:39 LOG7[3752:760]: SSL state (connect): SSLv3 read server hello A 2009.02.24 13:34:39 LOG7[3752:760]: SSL state (connect): SSLv3 read server certificate A 2009.02.24 13:34:39 LOG7[3752:760]: SSL state (connect): SSLv3 read server done A 2009.02.24 13:34:39 LOG7[3752:760]: SSL state (connect): SSLv3 write client key exchange A 2009.02.24 13:34:39 LOG7[3752:760]: SSL state (connect): SSLv3 write change cipher spec A 2009.02.24 13:34:39 LOG7[3752:760]: SSL state (connect): SSLv3 write finished A 2009.02.24 13:34:39 LOG7[3752:760]: SSL state (connect): SSLv3 flush data 2009.02.24 13:34:39 LOG7[3752:760]: SSL state (connect): SSLv3 read finished A 2009.02.24 13:34:39 LOG7[3752:760]: 1 items in the session cache 2009.02.24 13:34:39 LOG7[3752:760]: 1 client connects (SSL_connect()) 2009.02.24 13:34:39 LOG7[3752:760]: 1 client connects that finished 2009.02.24 13:34:39 LOG7[3752:760]: 0 client renegotiations requested 2009.02.24 13:34:39 LOG7[3752:760]: 0 server connects (SSL_accept()) 2009.02.24 13:34:39 LOG7[3752:760]: 0 server connects that finished 2009.02.24 13:34:39 LOG7[3752:760]: 0 server renegotiations requested 2009.02.24 13:34:39 LOG7[3752:760]: 0 session cache hits 2009.02.24 13:34:39 LOG7[3752:760]: 0 session cache misses 2009.02.24 13:34:39 LOG7[3752:760]: 0 session cache timeouts 2009.02.24 13:34:39 LOG6[3752:760]: SSL connected: new session negotiated 2009.02.24 13:34:39 LOG6[3752:760]: Negotiated ciphers: RC4-MD5 SSLv3 Kx=RSA Au=RSA Enc=RC4(128) Mac=MD5 2009.02.24 13:34:39 LOG7[3752:760]: SSL socket closed on SSL_read 2009.02.24 13:34:39 LOG7[3752:760]: Socket write shutdown 2009.02.24 13:34:39 LOG5[3752:760]: Connection closed: 20 bytes sent to SSL, 226 bytes sent to socket 2009.02.24 13:34:39 LOG7[3752:760]: smtp finished (0 left) 2009.02.24 13:34:39 LOG7[3752:1576]: pop accepted FD=232 from 127.0.0.1:3065 2009.02.24 13:34:39 LOG7[3752:1576]: Creating a new thread 2009.02.24 13:34:39 LOG7[3752:1576]: New thread created 2009.02.24 13:34:39 LOG7[3752:376]: pop started 2009.02.24 13:34:39 LOG7[3752:376]: FD 232 in non-blocking mode 2009.02.24 13:34:39 LOG7[3752:376]: TCP_NODELAY option set on local socket 2009.02.24 13:34:39 LOG5[3752:376]: pop accepted connection from 127.0.0.1:3065 2009.02.24 13:34:39 LOG7[3752:376]: FD 240 in non-blocking mode 2009.02.24 13:34:39 LOG7[3752:376]: pop connecting 209.85.147.109:995 2009.02.24 13:34:39 LOG7[3752:376]: connect_wait: waiting 10 seconds 2009.02.24 13:34:42 LOG7[3752:376]: connect_wait: connected 2009.02.24 13:34:42 LOG5[3752:376]: pop connected remote server from 192.168.1.100:3066 2009.02.24 13:34:42 LOG7[3752:376]: Remote FD=240 initialized 2009.02.24 13:34:42 LOG7[3752:376]: TCP_NODELAY option set on remote socket 2009.02.24 13:34:42 LOG7[3752:376]: SSL state (connect): before/connect initialization 2009.02.24 13:34:42 LOG7[3752:376]: SSL state (connect): SSLv3 write client hello A 2009.02.24 13:34:42 LOG7[3752:376]: SSL state (connect): SSLv3 read server hello A 2009.02.24 13:34:42 LOG7[3752:376]: SSL state (connect): SSLv3 read server certificate A 2009.02.24 13:34:42 LOG7[3752:376]: SSL state (connect): SSLv3 read server done A 2009.02.24 13:34:42 LOG7[3752:376]: SSL state (connect): SSLv3 write client key exchange A 2009.02.24 13:34:42 LOG7[3752:376]: SSL state (connect): SSLv3 write change cipher spec A 2009.02.24 13:34:42 LOG7[3752:376]: SSL state (connect): SSLv3 write finished A 2009.02.24 13:34:42 LOG7[3752:376]: SSL state (connect): SSLv3 flush data 2009.02.24 13:34:42 LOG7[3752:376]: SSL state (connect): SSLv3 read finished A 2009.02.24 13:34:42 LOG7[3752:376]: 1 items in the session cache 2009.02.24 13:34:42 LOG7[3752:376]: 1 client connects (SSL_connect()) 2009.02.24 13:34:42 LOG7[3752:376]: 1 client connects that finished 2009.02.24 13:34:42 LOG7[3752:376]: 0 client renegotiations requested 2009.02.24 13:34:42 LOG7[3752:376]: 0 server connects (SSL_accept()) 2009.02.24 13:34:42 LOG7[3752:376]: 0 server connects that finished 2009.02.24 13:34:42 LOG7[3752:376]: 0 server renegotiations requested 2009.02.24 13:34:42 LOG7[3752:376]: 0 session cache hits 2009.02.24 13:34:42 LOG7[3752:376]: 0 session cache misses 2009.02.24 13:34:42 LOG7[3752:376]: 0 session cache timeouts 2009.02.24 13:34:42 LOG6[3752:376]: SSL connected: new session negotiated 2009.02.24 13:34:42 LOG6[3752:376]: Negotiated ciphers: RC4-MD5 SSLv3 Kx=RSA Au=RSA Enc=RC4(128) Mac=MD5 2009.02.24 13:34:42 LOG7[3752:1576]: smtp accepted FD=264 from 127.0.0.1:3067 2009.02.24 13:34:42 LOG7[3752:1576]: Creating a new thread 2009.02.24 13:34:42 LOG7[3752:1576]: New thread created 2009.02.24 13:34:42 LOG7[3752:216]: smtp started 2009.02.24 13:34:42 LOG7[3752:216]: FD 264 in non-blocking mode 2009.02.24 13:34:42 LOG7[3752:216]: TCP_NODELAY option set on local socket 2009.02.24 13:34:42 LOG5[3752:216]: smtp accepted connection from 127.0.0.1:3067 2009.02.24 13:34:42 LOG7[3752:216]: FD 288 in non-blocking mode 2009.02.24 13:34:42 LOG7[3752:216]: smtp connecting 209.85.201.109:465 2009.02.24 13:34:42 LOG7[3752:216]: connect_wait: waiting 10 seconds 2009.02.24 13:34:42 LOG7[3752:216]: connect_wait: connected 2009.02.24 13:34:42 LOG5[3752:216]: smtp connected remote server from 192.168.1.100:3068 2009.02.24 13:34:42 LOG7[3752:216]: Remote FD=288 initialized 2009.02.24 13:34:42 LOG7[3752:216]: TCP_NODELAY option set on remote socket 2009.02.24 13:34:42 LOG7[3752:216]: SSL state (connect): before/connect initialization 2009.02.24 13:34:42 LOG7[3752:216]: SSL state (connect): SSLv3 write client hello A 2009.02.24 13:34:42 LOG7[3752:216]: SSL state (connect): SSLv3 read server hello A 2009.02.24 13:34:42 LOG7[3752:216]: SSL state (connect): SSLv3 read server certificate A 2009.02.24 13:34:42 LOG7[3752:216]: SSL state (connect): SSLv3 read server done A 2009.02.24 13:34:42 LOG7[3752:216]: SSL state (connect): SSLv3 write client key exchange A 2009.02.24 13:34:42 LOG7[3752:216]: SSL state (connect): SSLv3 write change cipher spec A 2009.02.24 13:34:42 LOG7[3752:216]: SSL state (connect): SSLv3 write finished A 2009.02.24 13:34:42 LOG7[3752:216]: SSL state (connect): SSLv3 flush data 2009.02.24 13:34:42 LOG7[3752:216]: SSL state (connect): SSLv3 read finished A 2009.02.24 13:34:42 LOG7[3752:216]: 2 items in the session cache 2009.02.24 13:34:42 LOG7[3752:216]: 2 client connects (SSL_connect()) 2009.02.24 13:34:42 LOG7[3752:216]: 2 client connects that finished 2009.02.24 13:34:42 LOG7[3752:216]: 0 client renegotiations requested 2009.02.24 13:34:42 LOG7[3752:216]: 0 server connects (SSL_accept()) 2009.02.24 13:34:42 LOG7[3752:216]: 0 server connects that finished 2009.02.24 13:34:42 LOG7[3752:216]: 0 server renegotiations requested 2009.02.24 13:34:42 LOG7[3752:216]: 0 session cache hits 2009.02.24 13:34:42 LOG7[3752:216]: 0 session cache misses 2009.02.24 13:34:42 LOG7[3752:216]: 0 session cache timeouts 2009.02.24 13:34:42 LOG6[3752:216]: SSL connected: new session negotiated 2009.02.24 13:34:42 LOG6[3752:216]: Negotiated ciphers: RC4-MD5 SSLv3 Kx=RSA Au=RSA Enc=RC4(128) Mac=MD5 2009.02.24 13:34:43 LOG3[3752:216]: readsocket: Connection reset by peer (WSAECONNRESET) (10054) 2009.02.24 13:34:43 LOG5[3752:216]: Connection reset: 63 bytes sent to SSL, 335 bytes sent to socket 2009.02.24 13:34:43 LOG7[3752:216]: smtp finished (1 left) 2009.02.24 13:35:43 LOG7[3752:376]: SSL socket closed on SSL_read 2009.02.24 13:35:43 LOG7[3752:376]: Socket write shutdown 2009.02.24 13:35:43 LOG5[3752:376]: Connection closed: 48 bytes sent to SSL, 131 bytes sent to socket 2009.02.24 13:35:43 LOG7[3752:376]: pop finished (0 left) Richard Brust rbrDataSolutions/ACT! Certified Consulting http://www.rbrDataSolutions.com 916/769-9411

1 0