Message 204323 - Python tracker

➜

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	Dima.Tisnek
Recipients	Dima.Tisnek, Dolf.Andringa, exarkun, giampaolo.rodola, grooverdan, janssen, jcea, markk, pdp, pitrou, scott.tsai
Date	2013-11-25.10:35:28
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1385375728.74.0.97086884449.issue5639@psf.upfronthosting.co.za>
In-reply-to

Content
Is this really not going into Python2 series? It's not a Python feature or a language feature, it's a matter of exporting OpenSSL feature. Furthermore it's a matter of security, same as support for session tickets is a matter of performance. SNI was first introduced in 2004, RFC in 2006, libcurl supported it from 2008, you had a patch since 2009 and still it's not in? Are you guys intentionally trying to cripple Python2? What do you think is likelier outcome, faster Python3 adoption or Python labelled insecure?

Is this really not going into Python2 series?

It's not a Python feature or a language feature, it's a matter of exporting OpenSSL feature.

Furthermore it's a matter of security, same as support for session tickets is a matter of performance.

SNI was first introduced in 2004, RFC in 2006, libcurl supported it from 2008, you had a patch since 2009 and still it's not in?

Are you guys intentionally trying to cripple Python2?

What do you think is likelier outcome, faster Python3 adoption or Python  labelled insecure?

History
Date	User	Action	Args
2013-11-25 10:35:28	Dima.Tisnek	set	recipients: + Dima.Tisnek, jcea, exarkun, janssen, pitrou, giampaolo.rodola, scott.tsai, pdp, grooverdan, Dolf.Andringa, markk
2013-11-25 10:35:28	Dima.Tisnek	set	messageid: <1385375728.74.0.97086884449.issue5639@psf.upfronthosting.co.za>
2013-11-25 10:35:28	Dima.Tisnek	link	issue5639 messages
2013-11-25 10:35:28	Dima.Tisnek	create