This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author j1m
Recipients christian.heimes, gvanrossum, j1m, r.david.murray, yselivanov
Date 2016-09-15.20:29:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1473971346.83.0.87031783694.issue27391@psf.upfronthosting.co.za>
In-reply-to
Content
SSL is used for more than just HTTP.  The are applications in which clients have server public keys that they use to authenticate servers rather than using certificate authorities.  For these applications, server host names are irrelevant.  This is why it makes sense to have an option on the SSL context to disable host name checking.  Removing this ability would break some applications.

If the option to check host names is provided as false on the SSL context, it makes no sense to check whether the host name, which isn't going to be used, is not None.  It's just silly, but not a huge deal one way or the other, because there are actually *two* ways to disable host name checking; you can also pass '' as the hostname, which is why this isn't a big deal and why I haven't gotten around to making a PR yet.
History
Date User Action Args
2016-09-15 20:29:06j1msetrecipients: + j1m, gvanrossum, christian.heimes, r.david.murray, yselivanov
2016-09-15 20:29:06j1msetmessageid: <1473971346.83.0.87031783694.issue27391@psf.upfronthosting.co.za>
2016-09-15 20:29:06j1mlinkissue27391 messages
2016-09-15 20:29:06j1mcreate