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

Specify servername when creating secureSocket over tunneling proxy #300

Closed
wants to merge 1 commit into from

Conversation

isaacs
Copy link
Contributor

@isaacs isaacs commented Aug 17, 2012

This makes the https-over-http proxy work when strictSSL is turned on.

In v0.8.4, we fixed a security bug where an otherwise valid cert would be
accepted for a host that was not listed in the CN or subjectaltnames
sections of the certificate.

However, this breaks proxying, because you want to accept the cert if
it comes from the origin server, not tested against the proxy's
hostname.

This fixes isaacs/npm#2719

This makes the https-over-http proxy work when strictSSL is turned on.

In v0.8.4, we fixed a bug where an otherwise valid cert would be
accepted for a host that was not listed in the CN or subjectaltnames
sections of the certificate.

However, this breaks proxying, because you want to accept the cert if
it comes from the origin server, not tested against the proxy's
hostname.

This fixes isaacs/npm#2719
@isaacs
Copy link
Contributor Author

isaacs commented Sep 4, 2012

duplicate, and pull from master. Closing in favor of #318

@isaacs isaacs closed this Sep 4, 2012
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.

None yet

1 participant