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 markk
Recipients Dolf.Andringa, exarkun, giampaolo.rodola, grooverdan, janssen, jcea, markk, pdp, pitrou, scott.tsai
Date 2013-07-03.12:05:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Python 2.7 is still used in production. 

Given the scarcity of IPv4-addresses — and with CDNs (think: Amazon, Akamai, EdgeCast…) starting to offer HTTP+SSL — the need for SNI arises in order to avoid pitfalls such as shared certificates.

The lack of ubiquitous support for TLS SNI could cause delays in HTTPS-everywhere–deployments. Therefore, in the light of the latest revelations about mass surveillance, I'd like even to argue that this is a matter of security and privacy.
Date User Action Args
2013-07-03 12:05:45markksetrecipients: + markk, jcea, exarkun, janssen, pitrou, giampaolo.rodola, scott.tsai, pdp, grooverdan, Dolf.Andringa
2013-07-03 12:05:45markksetmessageid: <>
2013-07-03 12:05:45markklinkissue5639 messages
2013-07-03 12:05:45markkcreate