Hi all,
I was tried stunnel 4.0.9 compiled with Openssl 0.9.7g on Redhat ES 3.0 and
got the telnets sessions disconnected with error messages in stunnel.log as
below:
SSL alert (write): fatal: bad record mac
SSL_read: 1408F455: error:1408F455:SSL routines:SSL3_GET_RECORD:decryption
failed or bad record mac
The same problem with stunnel 4.0.12 compiled with Openssl 0.9.8a
Tried to disable the option socket = a:SO_REUSEADDR=0 in stunne server
configuration file but still not help.
Thanks in advance for any help:
Full stunnel.log:
--------------------
2005.10.21 04:07:33 LOG5[19485:1]: stunnel 4.12 on i686-pc-linux-gnu
UCONTEXT+POLL+IPv4+LIBWRAP with OpenSSL 0.9.8a 11 Oct 2005
2005.10.21 04:07:33 LOG7[19485:1]: Snagged 64 random bytes from /dev/urandom
2005.10.21 04:07:33 LOG7[19485:1]: RAND_status claims sufficient entropy for
the PRNG
2005.10.21 04:07:33 LOG6[19485:1]: PRNG seeded successfully
2005.10.21 04:07:33 LOG7[19485:1]: Certificate:
/usr/local/stunnel/etc/stunnel/stunnel.pem
2005.10.21 04:07:33 LOG7[19485:1]: Key file:
/usr/local/stunnel/etc/stunnel/stunnel.pem
2005.10.21 04:07:33 LOG6[19485:1]: file ulimit = 1024 (can be changed with
'ulimit -n')
2005.10.21 04:07:33 LOG6[19485:1]: poll() used - no FD_SETSIZE limit for
file descriptors
2005.10.21 04:07:33 LOG5[19485:1]: 500 clients allowed
2005.10.21 04:07:33 LOG7[19485:1]: FD 4 in non-blocking mode
2005.10.21 04:07:33 LOG7[19485:1]: FD 5 in non-blocking mode
2005.10.21 04:07:33 LOG7[19485:1]: FD 6 in non-blocking mode
2005.10.21 04:07:33 LOG7[19485:1]: SO_REUSEADDR option set on accept socket
2005.10.21 04:07:33 LOG7[19485:1]: telnets bound to 192.168.34.35:992
2005.10.21 04:07:33 LOG7[19486:1]: Created pid file /stunnel.pid
2005.10.21 04:07:33 LOG5[19487:1]: stunnel 4.12 on i686-pc-linux-gnu
UCONTEXT+POLL+IPv4+LIBWRAP with OpenSSL 0.9.8a 11 Oct 2005
2005.10.21 04:07:33 LOG7[19487:1]: Snagged 64 random bytes from /dev/urandom
2005.10.21 04:07:33 LOG7[19487:1]: RAND_status claims sufficient entropy for
the PRNG
2005.10.21 04:07:33 LOG6[19487:1]: PRNG seeded successfully
2005.10.21 04:07:33 LOG6[19487:1]: file ulimit = 1024 (can be changed with
'ulimit -n')
2005.10.21 04:07:33 LOG6[19487:1]: poll() used - no FD_SETSIZE limit for
file descriptors
2005.10.21 04:07:33 LOG5[19487:1]: 500 clients allowed
2005.10.21 04:07:33 LOG7[19487:1]: FD 4 in non-blocking mode
2005.10.21 04:07:33 LOG7[19487:1]: FD 5 in non-blocking mode
2005.10.21 04:07:33 LOG7[19487:1]: FD 6 in non-blocking mode
2005.10.21 04:07:33 LOG7[19487:1]: SO_REUSEADDR option set on accept socket
2005.10.21 04:07:33 LOG7[19487:1]: soap bound to 127.0.0.1:44300
2005.10.21 04:07:33 LOG7[19488:1]: Created pid file /stunnel.pid
2005.10.21 04:09:30 LOG7[19486:1]: telnets accepted FD=7 from
65.94.188.47:60677
2005.10.21 04:09:30 LOG7[19486:1]: Creating a new context
2005.10.21 04:09:30 LOG7[19486:1]: Context 2 created
2005.10.21 04:09:30 LOG7[19486:2]: Context swap: 1 -> 2
2005.10.21 04:09:30 LOG7[19486:2]: telnets started
2005.10.21 04:09:30 LOG7[19486:2]: FD 7 in non-blocking mode
2005.10.21 04:09:30 LOG7[19486:2]: TCP_NODELAY option set on local socket
2005.10.21 04:09:30 LOG5[19486:2]: telnets connected from 65.94.188.47:60677
2005.10.21 04:09:30 LOG7[19486:2]: SSL state (accept): before/accept
initialization
2005.10.21 04:09:30 LOG7[19486:2]: SSL state (accept): SSLv3 read client
hello A
2005.10.21 04:09:30 LOG7[19486:2]: SSL state (accept): SSLv3 write server
hello A
2005.10.21 04:09:30 LOG7[19486:2]: SSL state (accept): SSLv3 write
certificate A
2005.10.21 04:09:30 LOG7[19486:2]: SSL state (accept): SSLv3 write server
done A
2005.10.21 04:09:30 LOG7[19486:2]: SSL state (accept): SSLv3 flush data
2005.10.21 04:09:30 LOG7[19486:2]: SSL state (accept): SSLv3 read client key
exchange A
2005.10.21 04:09:30 LOG7[19486:2]: SSL state (accept): SSLv3 read finished A
2005.10.21 04:09:30 LOG7[19486:2]: SSL state (accept): SSLv3 write change
cipher spec A
2005.10.21 04:09:30 LOG7[19486:2]: SSL state (accept): SSLv3 write finished
A
2005.10.21 04:09:30 LOG7[19486:2]: SSL state (accept): SSLv3 flush data
2005.10.21 04:09:30 LOG7[19486:2]: 1 items in the session cache
2005.10.21 04:09:30 LOG7[19486:2]: 0 client connects (SSL_connect())
2005.10.21 04:09:30 LOG7[19486:2]: 0 client connects that finished
2005.10.21 04:09:30 LOG7[19486:2]: 0 client renegotiatations requested
2005.10.21 04:09:30 LOG7[19486:2]: 1 server connects (SSL_accept())
2005.10.21 04:09:30 LOG7[19486:2]: 1 server connects that finished
2005.10.21 04:09:30 LOG7[19486:2]: 0 server renegotiatiations requested
2005.10.21 04:09:30 LOG7[19486:2]: 0 session cache hits
2005.10.21 04:09:30 LOG7[19486:2]: 0 session cache misses
2005.10.21 04:09:30 LOG7[19486:2]: 0 session cache timeouts
2005.10.21 04:09:30 LOG6[19486:2]: SSL accepted: new session negotiated
2005.10.21 04:09:30 LOG6[19486:2]: Negotiated ciphers: RC4-MD5
SSLv3 Kx=RSA Au=RSA Enc=RC4(128) Mac=MD5
2005.10.21 04:09:30 LOG7[19486:2]: FD 8 in non-blocking mode
2005.10.21 04:09:30 LOG7[19486:2]: telnets connecting 127.0.0.1:23
2005.10.21 04:09:30 LOG7[19486:2]: connect_wait: waiting 10 seconds
2005.10.21 04:09:30 LOG7[19486:2]: connect_wait: connected
2005.10.21 04:09:30 LOG7[19486:2]: Remote FD=8 initialized
2005.10.21 04:09:30 LOG7[19486:2]: TCP_NODELAY option set on remote socket
2005.10.21 04:09:31 LOG7[19488:1]: soap accepted FD=7 from 127.0.0.1:37120
2005.10.21 04:09:31 LOG7[19488:1]: Creating a new context
2005.10.21 04:09:31 LOG7[19488:1]: Context 2 created
2005.10.21 04:09:31 LOG7[19488:2]: Context swap: 1 -> 2
2005.10.21 04:09:31 LOG7[19488:2]: soap started
2005.10.21 04:09:31 LOG7[19488:2]: FD 7 in non-blocking mode
2005.10.21 04:09:31 LOG7[19488:2]: TCP_NODELAY option set on local socket
2005.10.21 04:09:31 LOG5[19488:2]: soap connected from 127.0.0.1:37120
2005.10.21 04:09:31 LOG7[19488:2]: FD 8 in non-blocking mode
2005.10.21 04:09:31 LOG7[19488:2]: soap connecting 199.84.230.35:443
2005.10.21 04:09:31 LOG7[19488:2]: connect_wait: waiting 10 seconds
2005.10.21 04:09:31 LOG7[19488:2]: connect_wait: connected
2005.10.21 04:09:31 LOG7[19488:2]: Remote FD=8 initialized
2005.10.21 04:09:31 LOG7[19488:2]: TCP_NODELAY option set on remote socket
2005.10.21 04:09:31 LOG7[19488:2]: SSL state (connect): before/connect
initialization
2005.10.21 04:09:31 LOG7[19488:2]: SSL state (connect): SSLv3 write client
hello A
2005.10.21 04:09:31 LOG7[19488:2]: SSL state (connect): SSLv3 read server
hello A
2005.10.21 04:09:31 LOG7[19488:2]: SSL state (connect): SSLv3 read server
certificate A
2005.10.21 04:09:31 LOG7[19488:2]: SSL state (connect): SSLv3 read server
key exchange A
2005.10.21 04:09:31 LOG7[19488:2]: SSL state (connect): SSLv3 read server
done A
2005.10.21 04:09:31 LOG7[19488:2]: SSL state (connect): SSLv3 write client
key exchange A
2005.10.21 04:09:31 LOG7[19488:2]: SSL state (connect): SSLv3 write change
cipher spec A
2005.10.21 04:09:31 LOG7[19488:2]: SSL state (connect): SSLv3 write finished
A
2005.10.21 04:09:31 LOG7[19488:2]: SSL state (connect): SSLv3 flush data
2005.10.21 04:09:31 LOG7[19488:2]: SSL state (connect): SSLv3 read finished
A
2005.10.21 04:09:31 LOG7[19488:2]: 1 items in the session cache
2005.10.21 04:09:31 LOG7[19488:2]: 1 client connects (SSL_connect())
2005.10.21 04:09:31 LOG7[19488:2]: 1 client connects that finished
2005.10.21 04:09:31 LOG7[19488:2]: 0 client renegotiatations requested
2005.10.21 04:09:31 LOG7[19488:2]: 0 server connects (SSL_accept())
2005.10.21 04:09:31 LOG7[19488:2]: 0 server connects that finished
2005.10.21 04:09:31 LOG7[19488:2]: 0 server renegotiatiations requested
2005.10.21 04:09:31 LOG7[19488:2]: 0 session cache hits
2005.10.21 04:09:31 LOG7[19488:2]: 0 session cache misses
2005.10.21 04:09:31 LOG7[19488:2]: 0 session cache timeouts
2005.10.21 04:09:31 LOG6[19488:2]: SSL connected: new session negotiated
2005.10.21 04:09:31 LOG6[19488:2]: Negotiated ciphers: DHE-RSA-AES256-SHA
SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1
2005.10.21 04:09:31 LOG7[19488:2]: SSL_read returned WANT_READ: retrying
2005.10.21 04:09:31 LOG7[19488:2]: SSL_read returned WANT_READ: retrying
2005.10.21 04:09:31 LOG7[19488:2]: SSL alert (read): warning: close notify
2005.10.21 04:09:31 LOG7[19488:2]: SSL closed on SSL_read
2005.10.21 04:09:31 LOG7[19488:2]: Socket write shutdown
2005.10.21 04:09:31 LOG7[19488:2]: SSL write shutdown
2005.10.21 04:09:31 LOG7[19488:2]: SSL alert (write): warning: close notify
2005.10.21 04:09:31 LOG6[19488:2]: SSL_shutdown successfully sent
close_notify
2005.10.21 04:09:31 LOG7[19488:2]: Socket closed on read
2005.10.21 04:09:31 LOG5[19488:2]: Connection closed: 818 bytes sent to SSL,
4558 bytes sent to socket
2005.10.21 04:09:31 LOG7[19488:2]: soap finished (0 left)
2005.10.21 04:09:31 LOG5[19488:2]: stack_info: size=65536, current=9560
(14%), maximum=9560 (14%)
2005.10.21 04:09:31 LOG7[19488:2]: Context 2 closed
2005.10.21 04:09:45 LOG7[19486:2]: SSL alert (write): fatal: bad record mac
2005.10.21 04:09:45 LOG3[19486:2]: SSL_read: 1408F455: error:1408F455:SSL
routines:SSL3_GET_RECORD:decryption failed or bad record mac
2005.10.21 04:09:45 LOG5[19486:2]: Connection reset: 4313 bytes sent to SSL,
232 bytes sent to socket
2005.10.21 04:09:45 LOG7[19486:2]: telnets finished (0 left)
2005.10.21 04:09:45 LOG5[19486:2]: stack_info: size=65536, current=9560
(14%), maximum=9560 (14%)
2005.10.21 04:09:45 LOG7[19486:2]: Context 2 closed
_________________________________________________________________
Take advantage of powerful junk e-mail filters built on patented Microsoft®
SmartScreen Technology.
http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=ht…
Start enjoying all the benefits of MSN® Premium right now and get the
first two months FREE*.
1
0
Hello,
I want to use a ECC-certificate for stunnel.pem, but it doesn't work.
Can anybody help me, what I have to do, to use Elliptique Curve cryptography
certificates in Stunnel? Is it still possible or not?
The ECC-Ciphers "ECDH-ECDSA-AES256-SHA" from openssl 0.9.8 works, but when I
loaded the certificate into stunnel,
there was follow messages in the log-file:
stunnel.log in Server
##################
error stack: 140B3009 : error:140B3009:SSL
routines:SSL_CTX_use_RSAPrivateKey_file:PEM lib
SSL_CTX_use_RSAPrivateKey_file: 607907F: error:0607907F:digital envelope
routines:EVP_PKEY_get1_RSA:expecting an rsa key
Server is down
##################
Thanks,
Dennis
2
1
1
0
Hi!
After using stunnel on several freebsd boxes i decided to
try it out on my mailserver..
Unfortunately it silently died after first connection..
( and with exitcode=0 )
debug = 7
Nothing more in the log than startup + a line about a
incomming connection on port 9143.. ( where i put my incomming imap )
Nothing in any log on the box..
Ok.. It might be my openssl freebsd version or stunnel version
so i started to upgrade everything..
Freebsd 4.4 -> 4.11 stunnel 4.05 -> 4.11 etc..
Well did it work.. Nop..;-)
Finally i found out after tryin ktrace that the problem was that
the tcpwrapper code killed me..
That's ok but there where no logging at all that the tcpwrapper silently
decided that i was comming from a blocked host..
It's up now without tcpwrapper enabled and works perfect..;-)
Is there any possibility to have stunnel to say something about
tcpwrapper problems..;-)
And not just die..;-)
Regards
/Uffe
4
9
I have a situation in which I have a client system, a middle-tier
application server, and a backend database. The middle-tier takes info
from the client and sends requests to the database, in other words the
middle-tier has to act as both a client and a server in different parts
of a transaction. Is it necessary that I run two instances of stunnel,
one with an stunnel-client.conf wherein client=yes and another instance
with stunnel-server.conf wherein client=no or is it possible to
configure a single stunnel to do this? I would guess it would be kind
of like having "client=yes|no" at the service level; this is not an
option as far as I can see from the man page for 4.12 but I figured I
could at least ask.
3
2
Hello
I've got problem with vnc over stunnel, stunnel on client computer
crashes all the time. I did all configuration according to
information at http://www.securityfocus.com/infocus/1677. Stunnel v
4.12, VNC version 4.1.1, all firewalls off, all computers in the
same LAN. Tried on Windows XP SP2 and Windows 2000, on both of them
there was a crash.
All necessery (at least I think so) information are here:
http://users.vlo.ids.gda.pl/~piotr/client.txt
http://users.vlo.ids.gda.pl/~piotr/server.txt
http://users.vlo.ids.gda.pl/~piotr/windows.txt
Thank you in advance
3
2
> > I've got problem with vnc over stunnel, stunnel on client computer
> > crashes all the time.
> Did you try to upgrade DLLs to the latest version:
> ftp://stunnel.mirt.net/stunnel/openssl/binary-0.9.8a-zdll/
I did upgrade librabries on both server and client, unfortunately it
didn't help - theres is still a crash. Should I generate certifcates
again? Meantime, I did configure it on my Ubuntu 10 X box, and
manage to connect with server, so I guess server configuration is ok.
Thanks for help.
Best regards.
2
1
Dear Sirs,
I want to use a ECC-certificate for stunnel.pem, but it doesn't work.
Can you tell me, what I have to do, to use Elliptique Curve cryptography
certificates in Stunnel? Is it still possible or not?
The ECC-Ciphers "ECDH-ECDSA-AES256-SHA" from openssl 0.9.8 works, but when I
loaded the certificate into stunnel,
there was follow messages in the log-file:
stunnel.log in Server
##################
error stack: 140B3009 : error:140B3009:SSL
routines:SSL_CTX_use_RSAPrivateKey_file:PEM lib
SSL_CTX_use_RSAPrivateKey_file: 607907F: error:0607907F:digital envelope
routines:EVP_PKEY_get1_RSA:expecting an rsa key
Server is down
##################
Best regards,
Dennis
1
0
Hi All,
I'd like to put stunnel in front of dbmail-imap and dbmail-pop, since
they don't offer any encryption. I understand I can just do straight
ssl connections, but would like [prefer] to support TLS.
I've found patches to the stunnel 3 series that implement TLS for
IMAP, but haven't found any for version 4.
Has someone implemented it for 4?
Is there a technical or political reason/problem, or just not enough
round-tuits?
Thanks,
g.
3
3
404 File Not Found when accessing webservice using STunnel (works fine without STunnel)
by Sundell Staffan 10 Oct '05
by Sundell Staffan 10 Oct '05
10 Oct '05
"stunnel 4.08 on x86-pc-mingw32-gnu WIN32+IPv6 with OpenSSL 0.9.7e 25
Oct 2004"
Hi, this is my first try with both SSL & STunnel, so please excuse me
for any missunderstandings a.s.o.
I have problems running a STunnel in client-mode agains a SSL
webservice.
Our application does not support clientside-certificates, so i want to
use STunnel to handle the SSL connection.
For now, our webservice-provider has disabled the need for
client-certificates (to help us narrow our problem down)
But it still dont work.
As a first step, i access whe webservice default-page through
IE-Explorer.
https://<ip>:3001/<path> and i am presented with the default-webpage.
As i second step, i start stunnel with following .conf
verify = 2
CApath = <path where i have saved all certificates as .pem:s with
<hash>.0 filenames, from the direct-access example with explorer above>
debug = 7
client = yes
[https]
accept = 127.0.0.1:3000
connect = <ip>:3001
TIMEOUTclose = 0
and try to access http://127.0.0.1:3000/<path>
but i get: HTTP 404 File Not found.
I have tried the same approach against a microsoft webservice at:
https://test.uddi.microsoft.com/extension.asmx
Without any problems.
1. I see no errors in the log, as i understand it (se below) can any one
else with a more skilled eye see any problem ?
2. Our webservice-provider has an invalid hostname in its certificate
(no public hostname, just IP during testing, but server certificate
state www.fora.se)
might that cause a problem ? (i have tried localy with invalid hostname
in certificate without any problem though)
3. Is it possible to enable/disable verification of hostname in STunnel
?
(as i understand it, the "verify" option in the STunnel.conf concerns
the whole certificate-validation-process, and not just the hostname
validation ?)
4. Could the problem be a config-issue on the webservice-provider end ?
Im not sure, as it works with IE-Explorer, but not through STunnel ?
5. Any clue on where to look would be greatly apriciated, i have been
working with this for a week, and i have been able to use STunnel both
as server & client, with & without client-certs against everything i
have tested localy and public (tried between diffrent home-made
applications, on a local webserver, against verisign website a.s.o.) and
everything works fine, except where i need it to work (against our
webservice-provider).
Regards
/Staffan Sundell
STunnel log against our webservice-provider (when it doesnt work):
2005.10.10 16:50:23 LOG5[2760:2800]: stunnel 4.08 on x86-pc-mingw32-gnu
WIN32+IPv6 with OpenSSL 0.9.7e 25 Oct 2004
2005.10.10 16:50:23 LOG7[2760:2332]: RAND_status claims sufficient
entropy for the PRNG
2005.10.10 16:50:23 LOG6[2760:2332]: PRNG seeded successfully
2005.10.10 16:50:23 LOG7[2760:2332]: Verify directory set to w:\ws\certs
2005.10.10 16:50:23 LOG5[2760:2332]: No limit detected for the number of
clients
2005.10.10 16:50:23 LOG7[2760:2332]: FD 1916 in non-blocking mode
2005.10.10 16:50:23 LOG7[2760:2332]: SO_REUSEADDR option set on accept
socket
2005.10.10 16:50:23 LOG7[2760:2332]: https bound to 127.0.0.1:3000
2005.10.10 16:50:28 LOG7[2760:2332]: https accepted FD=1904 from
127.0.0.1:2975
2005.10.10 16:50:28 LOG7[2760:2332]: FD 1904 in non-blocking mode
2005.10.10 16:50:28 LOG7[2760:2332]: Creating a new thread
2005.10.10 16:50:28 LOG7[2760:2332]: New thread created
2005.10.10 16:50:28 LOG7[2760:3748]: https started
2005.10.10 16:50:28 LOG5[2760:3748]: https connected from 127.0.0.1:2975
2005.10.10 16:50:28 LOG7[2760:3748]: FD 1876 in non-blocking mode
2005.10.10 16:50:28 LOG7[2760:3748]: https connecting
<webserviceprovider ip>:3001
2005.10.10 16:50:28 LOG7[2760:3748]: connect_wait: waiting 10 seconds
2005.10.10 16:50:28 LOG7[2760:3748]: connect_wait: connected
2005.10.10 16:50:28 LOG7[2760:3748]: Remote FD=1876 initialized
2005.10.10 16:50:28 LOG7[2760:3748]: SSL state (connect): before/connect
initialization
2005.10.10 16:50:28 LOG7[2760:3748]: SSL state (connect): SSLv3 write
client hello A
2005.10.10 16:50:28 LOG7[2760:3748]: SSL state (connect): SSLv3 read
server hello A
2005.10.10 16:50:28 LOG5[2760:3748]: VERIFY OK: depth=2,
/C=US/O=VeriSign, Inc./OU=Class 3 Public Primary Certification Authority
2005.10.10 16:50:28 LOG5[2760:3748]: VERIFY OK: depth=1, /O=VeriSign
Trust Network/OU=VeriSign, Inc./OU=VeriSign International Server CA -
Class 3/OU=www.verisign.com/CPS Incorp.by Ref. LIABILITY LTD.(c)97
VeriSign
2005.10.10 16:50:28 LOG5[2760:3748]: VERIFY OK: depth=0,
/C=SE/L=STOCKHOLM/O=Fora AB/OU=Member, VeriSign Trust Network/OU=Terms
of use at www.verisign.se/rpa <http://www.verisign.se/rpa>
(c)05/OU=Authenticated by VeriSign/OU=Member, VeriSign Trust
Network/CN=www.fora.se
2005.10.10 16:50:28 LOG7[2760:3748]: SSL state (connect): SSLv3 read
server certificate A
2005.10.10 16:50:28 LOG7[2760:3748]: SSL state (connect): SSLv3 read
server done A
2005.10.10 16:50:28 LOG7[2760:3748]: SSL state (connect): SSLv3 write
client key exchange A
2005.10.10 16:50:28 LOG7[2760:3748]: SSL state (connect): SSLv3 write
change cipher spec A
2005.10.10 16:50:28 LOG7[2760:3748]: SSL state (connect): SSLv3 write
finished A
2005.10.10 16:50:28 LOG7[2760:3748]: SSL state (connect): SSLv3 flush
data
2005.10.10 16:50:28 LOG7[2760:3748]: SSL state (connect): SSLv3 read
finished A
2005.10.10 16:50:28 LOG7[2760:3748]: 1 items in the session cache
2005.10.10 16:50:28 LOG7[2760:3748]: 1 client connects
(SSL_connect())
2005.10.10 16:50:28 LOG7[2760:3748]: 1 client connects that finished
2005.10.10 16:50:28 LOG7[2760:3748]: 0 client renegotiatations
requested
2005.10.10 16:50:28 LOG7[2760:3748]: 0 server connects (SSL_accept())
2005.10.10 16:50:28 LOG7[2760:3748]: 0 server connects that finished
2005.10.10 16:50:28 LOG7[2760:3748]: 0 server renegotiatiations
requested
2005.10.10 16:50:28 LOG7[2760:3748]: 0 session cache hits
2005.10.10 16:50:28 LOG7[2760:3748]: 0 session cache misses
2005.10.10 16:50:28 LOG7[2760:3748]: 0 session cache timeouts
2005.10.10 16:50:28 LOG6[2760:3748]: SSL connected: new session
negotiated
2005.10.10 16:50:28 LOG6[2760:3748]: Negotiated ciphers: AES256-SHA
SSLv3 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA1
2005.10.10 16:50:45 LOG7[2760:3748]: SSL socket closed on SSL_read
2005.10.10 16:50:45 LOG7[2760:3748]: Socket write shutdown
2005.10.10 16:50:45 LOG5[2760:3748]: Connection closed: 407 bytes sent
to SSL, 507 bytes sent to socket
2005.10.10 16:50:45 LOG7[2760:3748]: https finished (0 left)
STunnel log against microsoft (where it works)
2005.10.10 16:50:22 LOG5[2940:2556]: stunnel 4.08 on x86-pc-mingw32-gnu
WIN32+IPv6 with OpenSSL 0.9.7e 25 Oct 2004
2005.10.10 16:50:22 LOG7[2940:1112]: RAND_status claims sufficient
entropy for the PRNG
2005.10.10 16:50:22 LOG6[2940:1112]: PRNG seeded successfully
2005.10.10 16:50:22 LOG7[2940:1112]: Verify directory set to c:\ws\certs
2005.10.10 16:50:22 LOG5[2940:1112]: No limit detected for the number of
clients
2005.10.10 16:50:22 LOG7[2940:1112]: FD 136 in non-blocking mode
2005.10.10 16:50:22 LOG7[2940:1112]: SO_REUSEADDR option set on accept
socket
2005.10.10 16:50:22 LOG7[2940:1112]: https bound to 127.0.0.1:80
2005.10.10 16:50:32 LOG7[2940:1112]: https accepted FD=148 from
127.0.0.1:2977
2005.10.10 16:50:32 LOG7[2940:1112]: FD 148 in non-blocking mode
2005.10.10 16:50:32 LOG7[2940:1112]: Creating a new thread
2005.10.10 16:50:32 LOG7[2940:1112]: New thread created
2005.10.10 16:50:32 LOG7[2940:3904]: https started
2005.10.10 16:50:32 LOG5[2940:3904]: https connected from 127.0.0.1:2977
2005.10.10 16:50:32 LOG7[2940:3904]: FD 176 in non-blocking mode
2005.10.10 16:50:32 LOG7[2940:3904]: https connecting 207.46.197.39:443
2005.10.10 16:50:32 LOG7[2940:3904]: connect_wait: waiting 10 seconds
2005.10.10 16:50:33 LOG7[2940:3904]: connect_wait: connected
2005.10.10 16:50:33 LOG7[2940:3904]: Remote FD=176 initialized
2005.10.10 16:50:33 LOG7[2940:3904]: SSL state (connect): before/connect
initialization
2005.10.10 16:50:33 LOG7[2940:3904]: SSL state (connect): SSLv3 write
client hello A
2005.10.10 16:50:33 LOG7[2940:3904]: SSL state (connect): SSLv3 read
server hello A
2005.10.10 16:50:33 LOG5[2940:3904]: VERIFY OK: depth=3, /C=US/O=GTE
Corporation/OU=GTE CyberTrust Solutions, Inc./CN=GTE CyberTrust Global
Root
2005.10.10 16:50:33 LOG5[2940:3904]: VERIFY OK: depth=2, /CN=Microsoft
Internet Authority
2005.10.10 16:50:33 LOG5[2940:3904]: VERIFY OK: depth=1,
/DC=com/DC=microsoft/DC=corp/DC=redmond/CN=Microsoft Secure Server
Authority
2005.10.10 16:50:33 LOG5[2940:3904]: VERIFY OK: depth=0,
/C=US/ST=Washington/L=Redmond/O=Microsoft/OU=UDDI Test production
site/CN=test.uddi.microsoft.com
2005.10.10 16:50:33 LOG7[2940:3904]: SSL state (connect): SSLv3 read
server certificate A
2005.10.10 16:50:33 LOG7[2940:3904]: SSL state (connect): SSLv3 read
server done A
2005.10.10 16:50:33 LOG7[2940:3904]: SSL state (connect): SSLv3 write
client key exchange A
2005.10.10 16:50:33 LOG7[2940:3904]: SSL state (connect): SSLv3 write
change cipher spec A
2005.10.10 16:50:33 LOG7[2940:3904]: SSL state (connect): SSLv3 write
finished A
2005.10.10 16:50:33 LOG7[2940:3904]: SSL state (connect): SSLv3 flush
data
2005.10.10 16:50:33 LOG7[2940:3904]: SSL state (connect): SSLv3 read
finished A
2005.10.10 16:50:33 LOG7[2940:3904]: 1 items in the session cache
2005.10.10 16:50:33 LOG7[2940:3904]: 1 client connects
(SSL_connect())
2005.10.10 16:50:33 LOG7[2940:3904]: 1 client connects that finished
2005.10.10 16:50:33 LOG7[2940:3904]: 0 client renegotiatations
requested
2005.10.10 16:50:33 LOG7[2940:3904]: 0 server connects (SSL_accept())
2005.10.10 16:50:33 LOG7[2940:3904]: 0 server connects that finished
2005.10.10 16:50:33 LOG7[2940:3904]: 0 server renegotiatiations
requested
2005.10.10 16:50:33 LOG7[2940:3904]: 0 session cache hits
2005.10.10 16:50:33 LOG7[2940:3904]: 0 session cache misses
2005.10.10 16:50:33 LOG7[2940:3904]: 0 session cache timeouts
2005.10.10 16:50:33 LOG6[2940:3904]: SSL connected: new session
negotiated
2005.10.10 16:50:33 LOG6[2940:3904]: Negotiated ciphers: RC4-MD5
SSLv3 Kx=RSA Au=RSA Enc=RC4(128) Mac=MD5
2005.10.10 16:51:38 LOG3[2940:3904]: readsocket: Connection reset by
peer (WSAECONNRESET) (10054)
2005.10.10 16:51:38 LOG5[2940:3904]: Connection reset: 203 bytes sent to
SSL, 3214 bytes sent to socket
2005.10.10 16:51:38 LOG7[2940:3904]: https finished (0 left)
1
0