I'm running an HTTPS server and occasionally get client-side errors when trying to send
it a request from a client using OpenSSL.
The error I get from Ruby is:
/usr/lib/ruby/1.9.1/net/http.rb:678:in `connect': SSL_connect returned=1 errno=0
state=SSLv3 read server key exchange B: bad signature (OpenSSL::SSL::SSLError)
from /usr/lib/ruby/1.9.1/net/http.rb:678:in `block in connect'
from /usr/lib/ruby/1.9.1/timeout.rb:44:in `timeout'
from /usr/lib/ruby/1.9.1/timeout.rb:89:in `timeout'
from /usr/lib/ruby/1.9.1/net/http.rb:678:in `connect'
from /usr/lib/ruby/1.9.1/net/http.rb:637:in `do_start'
from /usr/lib/ruby/1.9.1/net/http.rb:626:in `start'
from /usr/lib/ruby/1.9.1/net/http.rb:1168:in `request'
from /usr/lib/ruby/1.9.1/net/http.rb:1081:in `request_get'
from testssl.rb:8:in `block in <main>'
from testssl.rb:6:in `times'
from testssl.rb:6:in `<main>'
I've attached a basic HTTPS server and a short Ruby script that can reproduce this
issue. The client makes 1000 requests against the server and this has always been enough
to trigger the problem for me.
Attachments:
- server.go (185 bytes)
- testssl.rb (189 bytes)
I'm running an HTTPS server and occasionally get client-side errors when trying to send it a request from a client using OpenSSL. The error I get from Ruby is: /usr/lib/ruby/1.9.1/net/http.rb:678:in `connect': SSL_connect returned=1 errno=0 state=SSLv3 read server key exchange B: bad signature (OpenSSL::SSL::SSLError) from /usr/lib/ruby/1.9.1/net/http.rb:678:in `block in connect' from /usr/lib/ruby/1.9.1/timeout.rb:44:in `timeout' from /usr/lib/ruby/1.9.1/timeout.rb:89:in `timeout' from /usr/lib/ruby/1.9.1/net/http.rb:678:in `connect' from /usr/lib/ruby/1.9.1/net/http.rb:637:in `do_start' from /usr/lib/ruby/1.9.1/net/http.rb:626:in `start' from /usr/lib/ruby/1.9.1/net/http.rb:1168:in `request' from /usr/lib/ruby/1.9.1/net/http.rb:1081:in `request_get' from testssl.rb:8:in `block in <main>' from testssl.rb:6:in `times' from testssl.rb:6:in `<main>' I've attached a basic HTTPS server and a short Ruby script that can reproduce this issue. The client makes 1000 requests against the server and this has always been enough to trigger the problem for me.Attachments: