We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi folks
The logic about ssl certificate verification in https://github.com/ncr/rack-proxy/blob/ce04ba5a15dd0c32d3f1b223fc980e3210f8008e/lib/rack/proxy.rb is pretty confusing.
There are two variables interacting - ssl_verify_none and verify_mode. imho we should only have one. Or are they doing different things entirely?
ssl_verify_none
verify_mode
https://github.com/ncr/rack-proxy#using-ssltls-certificates-with-http-connection doesn't specifically make it clear that unless you supply verify_mode: OpenSSL::SSL::VERIFY_PEER it'll default to OpenSSL::SSL::VERIFY_NONE which is a really bad default. At least, that's my reading of the code!
verify_mode: OpenSSL::SSL::VERIFY_PEER
OpenSSL::SSL::VERIFY_NONE
Context: http://www.rubyinside.com/how-to-cure-nethttps-risky-default-https-behavior-4010.html
The text was updated successfully, but these errors were encountered:
At the very least I'd propose changing OpenSSL::SSL::VERIFY_NONE in the two places it's used in proxy.rb to refer to OpenSSL::SSL::VERIFY_NONE
Sorry, something went wrong.
@ncr - not sure if you've had a look at this?
No branches or pull requests
Hi folks
The logic about ssl certificate verification in https://github.com/ncr/rack-proxy/blob/ce04ba5a15dd0c32d3f1b223fc980e3210f8008e/lib/rack/proxy.rb is pretty confusing.
There are two variables interacting -
ssl_verify_none
andverify_mode
. imho we should only have one. Or are they doing different things entirely?https://github.com/ncr/rack-proxy#using-ssltls-certificates-with-http-connection doesn't specifically make it clear that unless you supply
verify_mode: OpenSSL::SSL::VERIFY_PEER
it'll default toOpenSSL::SSL::VERIFY_NONE
which is a really bad default. At least, that's my reading of the code!Context: http://www.rubyinside.com/how-to-cure-nethttps-risky-default-https-behavior-4010.html
The text was updated successfully, but these errors were encountered: