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 benjamin.peterson
Recipients alex, benjamin.peterson, lemburg, r.david.murray
Date 2014-12-11.20:26:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1418329590.2570749.201827961.6C1B2B49@webmail.messagingengine.com>
In-reply-to <5489FD63.9020803@egenix.com>
Content
On Thu, Dec 11, 2014, at 15:24, Marc-Andre Lemburg wrote:
> 
> Marc-Andre Lemburg added the comment:
> 
> On 11.12.2014 20:42, Benjamin Peterson wrote:
> > 
> > Usually you can pass your own context.
> 
> Yes, in new code, but not in existing Python 2.7 code that wasn't
> written for the newly added SSL context feature.

How is modifying code to use a context different from modifying it to
mess around with a hypothetical ssl.DEFAULT_SSL_OPTIONS?

> 
> BTW: Having a way to change the SSL options globally would be useful
> for Python 3.x as well, since OpenSSL often adds new options and
> it's not unlikely we'll see an OP_NO_TLSv1 option soon, given its
> age and similarity to SSLv3...
> https://www.imperialviolet.org/2014/12/08/poodleagain.html
> (the poodle strikes back ;-))

That option already exists and is exposed. :)
History
Date User Action Args
2014-12-11 20:26:32benjamin.petersonsetrecipients: + benjamin.peterson, lemburg, alex, r.david.murray
2014-12-11 20:26:32benjamin.petersonlinkissue22866 messages
2014-12-11 20:26:32benjamin.petersoncreate