Forum Moderators: phranque

Message Too Old, No Replies

SSL timing out, SSL handshake failed

         

Tonearm

6:25 pm on Dec 5, 2002 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Hello, I've been getting SSL timed out and SSL handshake failed in my Apache server's access_ssl_log sometimes. The following log from yesterday had a bunch of them, but it looks like it was from only a couple IPs:

[Wed Dec 4 18:55:06 2002] [error] mod_ssl: SSL handshake timed out (client 111.222.333.444, server www.mystore.com:443)
[Wed Dec 4 18:55:06 2002] [error] mod_ssl: SSL handshake timed out (client 111.222.333.444, server www.mystore.com:443)
[Wed Dec 4 18:55:07 2002] [error] mod_ssl: SSL handshake timed out (client 111.222.333.444, server www.mystore.com:443)
[Wed Dec 4 18:55:07 2002] [error] mod_ssl: SSL handshake timed out (client 111.222.333.444, server www.mystore.com:443)
[Wed Dec 4 18:55:07 2002] [error] mod_ssl: SSL handshake timed out (client 111.222.333.444, server www.mystore.com:443)
[Wed Dec 4 18:55:07 2002] [error] mod_ssl: SSL handshake timed out (client 111.222.333.444, server www.mystore.com:443)
[Wed Dec 4 18:55:07 2002] [error] mod_ssl: SSL handshake timed out (client 111.222.333.444, server www.mystore.com:443)
[Wed Dec 4 18:55:08 2002] [error] mod_ssl: SSL handshake failed (server www.mystore.com:443, client 111.222.333.444) (OpenSSL library error follows)
[Wed Dec 4 18:55:08 2002] [error] OpenSSL: error:1406B458:SSL routines:GET_CLIENT_MASTER_KEY:key arg too long
[Thu Dec 5 01:44:10 2002] [error] mod_ssl: SSL handshake timed out (client 111.222.333.444, server www.mystore.com:443)
[Thu Dec 5 01:44:12 2002] [error] mod_ssl: SSL handshake timed out (client 111.222.333.444, server www.mystore.com:443)
[Thu Dec 5 01:44:14 2002] [error] mod_ssl: SSL handshake timed out (client 111.222.333.444, server www.mystore.com:443)
[Thu Dec 5 01:44:15 2002] [error] mod_ssl: SSL handshake timed out (client 111.222.333.444, server www.mystore.com:443)
[Thu Dec 5 01:44:15 2002] [error] mod_ssl: SSL handshake timed out (client 111.222.333.444, server www.mystore.com:443)
[Thu Dec 5 01:44:15 2002] [error] mod_ssl: SSL handshake timed out (client 111.222.333.444, server www.mystore.com:443)
[Thu Dec 5 01:44:16 2002] [error] mod_ssl: SSL handshake timed out (client 111.222.333.444, server www.mystore.com:443)
[Thu Dec 5 01:44:16 2002] [error] mod_ssl: SSL handshake timed out (client 111.222.333.444, server www.mystore.com:443)
[Thu Dec 5 01:44:16 2002] [error] mod_ssl: SSL handshake timed out (client 111.222.333.444, server www.mystore.com:443)
[Thu Dec 5 01:44:16 2002] [error] mod_ssl: SSL handshake failed (server www.mystore.com:443, client 111.222.333.444) (OpenSSL library error follows)
[Thu Dec 5 01:44:16 2002] [error] OpenSSL: error:1406B458:SSL routines:GET_CLIENT_MASTER_KEY:key arg too long

My website monitoring service (Pingalink) has been reporting "slow" status intermittently for a few weeks now. It's set to report slow when it takes longer than 1000ms to respond. Maybe that has something to do with it? I'm a bit worried about these errors as my checkout page is one of the only SSL pages on my site. Can anyone help with any ideas?

[edited by: oilman at 11:07 pm (utc) on Dec. 9, 2002]
[edit reason] edited IP #'s to generic #'s [/edit]

sugarkane

8:07 pm on Dec 9, 2002 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I don't think it's anything to worry about.

Have you recently patched Apache/SSL?

What I think is happening is that someone is trying - and failing - to exploit a now-fixed vulnerability in OpenSSL. The fact that you're getting timeouts shows that the hack attempts (probably just automated script stuff) are failing...

(Disclaimer: you might sleep better if you consult a security specialist on this ;) )

Added: "SSL routines:GET_CLIENT_MASTER_KEY:key arg too long"

Yep, they're trying the recent buffer overflow exploit (Slapper?)

Tonearm

9:06 pm on Dec 9, 2002 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Thanks a lot for the response. What version of Apache and SSL should I be running in order to be "safe"?

sugarkane

9:14 pm on Dec 9, 2002 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



The vulnerability was fixed in OpenSSL 0.9.6e

More info here [cert.org]