From: ben@...10r.com Date: 2016-12-09T18:14:32+00:00 Subject: [ruby-core:78561] [Ruby trunk Bug#10613] SNI is not optional when using TLS Issue #10613 has been updated by Ben Schmeckpeper. Is there any chance of this patch getting merged? We're encountering this bug and are currently monkeypatching the Net::HTTP#connect method to disable SNI for the connections where it's problematic. ---------------------------------------- Bug #10613: SNI is not optional when using TLS https://bugs.ruby-lang.org/issues/10613#change-61944 * Author: Eddy Kim * Status: Assigned * Priority: Normal * Assignee: Yui NARUSE * ruby -v: 2.1 * Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN ---------------------------------------- If ruby is using openssl with TLS extensions, and we attempt to connect to a server which supports TLS, but not SNI, the connection fails. e.g.: ~~~Ruby uri = URI.parse("https://example.com") # a server that supports TLSv1 but not the TLS extensions http = Net::HTTP.new(uri.host, uri.port) http.use_ssl = true http.ssl_version = :TLSv1 http.verify_mode = OpenSSL::SSL::VERIFY_PEER response = http.get(url) ~~~ ~~~ OpenSSL::SSL::SSLError: SSL_connect returned=1 errno=0 state=SSLv3 read server hello B: parse tlsext ~~~ If I patch the `Net::HTTP#connect` method to not assign the hostname to the socket (s), we can avoid this error. ---Files-------------------------------- optional-sni.patch (1019 Bytes) -- https://bugs.ruby-lang.org/ Unsubscribe: