Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VERIFY_PEER by default - no need for a cert_store option #20

Merged
merged 1 commit into from
Aug 1, 2016

Conversation

mohamedhafez
Copy link
Contributor

Testing all the way back to ruby 2.1.10, the last supported version of ruby still supported, if we don't specify the cert store and leave out the line http.verify_mode = OpenSSL::SSL::VERIFY_NONE, ruby will use its own cert store by default and conduct VERIFY_PEER verification. I can't see any reason why this shouldn't be the default...

Also, since Ruby's default cert_store is capable of verifying our small set of endpoints, I don't think we need an option to specify a custom cert_store so I've removed that as well

@mohamedhafez
Copy link
Contributor Author

@zaru or @rossta could you take a look at this? I'm 99% certain I'm correct here, and that not doing the ssl peer verification by default is a big, unnecessary security hole...

@rossta
Copy link
Collaborator

rossta commented Jul 27, 2016

Yes, I support the change to switch to VERIFY_PEER by default.

If needed, we could later provide an http_options option instead and pass that directly to HTTP.start to allow for control over HTTP behavior.

rjpaskin added a commit to cookieshq/browser-notifications-example that referenced this pull request Jul 29, 2016
@zaru zaru merged commit 9cf196e into zaru:master Aug 1, 2016
@zaru
Copy link
Owner

zaru commented Aug 1, 2016

@mohamedhafez sorry! I had missed.
Certainly it VERIFY_PEER is the better of the default.
Thanks for PR.

@mohamedhafez
Copy link
Contributor Author

no worries, thanks for merging @zaru !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants