➜

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 christian.heimes
Recipients alex, christian.heimes, dstufft, janssen, samiam
Date 2017-11-10.07:59:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1510300757.24.0.213398074469.issue31997@psf.upfronthosting.co.za>
In-reply-to
Content 
Trailing dots in hostname seem to be protocol specific, e.g. SMTP does not allow them. Unless you find a RFC that mandates support for trailing dots in TLS, I'm against a change in Python's TLS stack. It's too risky to mess up SNI, too.

I'd rather follow RFC 5890, make the caller deal with FQDN + trailing dot and require libraries to pass in a DNS Domain Names (a fully qualified domain name without a trailing dot) to server_hostname.

https://tools.ietf.org/html/rfc6125#section-2.2
https://tools.ietf.org/html/rfc5890#section-2.2

   (The complete name convention using a trailing dot described
   in RFC 1123 [RFC1123], which can be explicit as in "www.example.com."
   or implicit as in "www.example.com", is not considered in this
   specification.)
History
Date User Action Args
2017-11-10 07:59:17christian.heimessetrecipients: + christian.heimes, janssen, alex, dstufft, samiam
2017-11-10 07:59:17christian.heimessetmessageid: <1510300757.24.0.213398074469.issue31997@psf.upfronthosting.co.za>
2017-11-10 07:59:17christian.heimeslinkissue31997 messages
2017-11-10 07:59:16christian.heimescreate