https://bugs.ruby-lang.org/https://bugs.ruby-lang.org/favicon.ico?17113305112011-08-01T00:54:33ZRuby Issue Tracking SystemRuby master - Bug #5110: Ruby SSL error - sslv3 alert unexpected messagehttps://bugs.ruby-lang.org/issues/5110?journal_id=198742011-08-01T00:54:33ZMartinBosslet (Martin Bosslet)Martin.Bosslet@gmail.com
<ul><li><strong>Category</strong> set to <i>ext</i></li><li><strong>Status</strong> changed from <i>Open</i> to <i>Feedback</i></li><li><strong>Assignee</strong> set to <i>MartinBosslet (Martin Bosslet)</i></li><li><strong>Target version</strong> set to <i>1.9.3</i></li></ul><p>In my opinion Ruby reacts normal here. The OpenSSL::SSL::SSLContext is allocated using "SSLv23" by default for maximum compatibility. Here is what the official doc says:</p>
<p>SSLv23_method:</p>
<p>A TLS/SSL connection established with these methods will understand the SSLv2, SSLv3, and TLSv1 protocol. A client will send out SSLv2 client hello messages and will indicate that it also understands SSLv3 and TLSv1. A server will understand SSLv2, SSLv3, and TLSv1 client hello messages. This is the best choice when compatibility is a concern.</p>
<p>I checked, the server you mentions does accept v3 client hello messages only, so it does not recognize in particular the v2 message that is sent by default. I'd suggest that it is fine to blame the server for being inflexible in your case.</p>
<p>Do you agree?</p>
<p>Regards,<br>
Martin</p> Ruby master - Bug #5110: Ruby SSL error - sslv3 alert unexpected messagehttps://bugs.ruby-lang.org/issues/5110?journal_id=214102011-10-19T11:14:26ZMartinBosslet (Martin Bosslet)Martin.Bosslet@gmail.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Closed</i></li></ul><p>If nobody disagrees, I would like to close this.</p>