Turning off verify_mode for SSL

Ruby
1

Hi!

In my rails tests, I get the warnings: warning: peer certificate won’t
be
verified in this SSL session

I found this on the ruby list:

Hi,

I’ve got a little Ruby script that needs to use SSL but doesn’t really
worry about authentication at all. Here’s the relevant code:

  https = Net::HTTP.new(URL, 443)
  https.use_ssl = true
  data = ""
  https.start{|h|
    h.get2(url) {|resp|
      data = resp.body
    }
  }

When I run this, it works great but gives me (on STDERR):
peer certificate won’t be verified in this SSL session

I don’t really care about the verification, so how should I turn this
warning off or otherwise prevent it from printing?

Thanks,
Keith

and the response:

K> https = Net::HTTP.new(URL, 443)
K> https.use_ssl = true

     https.verify_mode = OpenSSL::SSL::VERIFY_NONE

K> data = “”
K> https.start{|h|
K> h.get2(url) {|resp|
K> data = resp.body
K> }
K> }

now my question: is it possible to turn https.verify_mode =
OpenSSL::SSL::VERIFY_NONE on for all new Net::HTTP instances? I want to
prevent getting that warning while I run my tests.

Thanks, Rob

2

On Apr 19, 10:43 am, “Robert MannI” [email protected] wrote:

worry about authentication at all. Here’s the relevant code:
When I run this, it works great but gives me (on STDERR):
K> https = Net::HTTP.new(URL, 443)

now my question: is it possible to turn https.verify_mode =
OpenSSL::SSL::VERIFY_NONE on for all new Net::HTTP instances? I want to
prevent getting that warning while I run my tests.

Thanks, Rob

Hi Rob,

I found this page via Google, http://devmates.com/archive/48/

HTH.

Regards,

Chris

3

Hi Celldee,

thanks, but that just solves the problem if you already have a net/http
instance var, in that case @http.

I need to solve this for all my Net::HTTP instances.

Best, Rob

4

Robert MannI wrote:

Hi Celldee,

thanks, but that just solves the problem if you already have a
net/http
instance var, in that case @http.

I need to solve this for all my Net::HTTP instances.

Best, Rob

Firstly:
A: Because it makes it difficult to associate responses.
Q: Why is top-quoting bad?

Secondly:
Subclass Net::HTTP, and enhance the initialize method in your
application?

–
Phillip “CynicalRyan” Gawlowski
http://cynicalryan.110mb.com/
http://clothred.rubyforge.org

Rule of Open-Source Programming #20:

Open Code != Good Code