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 ncoghlan
Recipients alex, christian.heimes, dstufft, giampaolo.rodola, janssen, kushal.das, ncoghlan, ned.deily, pitrou, suki
Date 2015-07-05.10:56:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1436093780.76.0.239357415454.issue23965@psf.upfronthosting.co.za>
In-reply-to
Content
Yeah, I belatedly realised I was overcomplicating things, and the test failures really are just due the change in the context options to disallow SSLv3 peers by default.

I have an idea for how to fix that, and I think it will make the handling of the NO_SSLv2 flag in the SSL tests easier to follow as well.

It's also worth noting that https://www.rfc-editor.org/info/rfc7568 was published recently to start deprecating SSL 3.0 entirely, so setting that flag by default is indeed going to become the norm at the distro layer.
History
Date User Action Args
2015-07-05 10:56:20ncoghlansetrecipients: + ncoghlan, janssen, pitrou, giampaolo.rodola, christian.heimes, ned.deily, alex, kushal.das, dstufft, suki
2015-07-05 10:56:20ncoghlansetmessageid: <1436093780.76.0.239357415454.issue23965@psf.upfronthosting.co.za>
2015-07-05 10:56:20ncoghlanlinkissue23965 messages
2015-07-05 10:56:20ncoghlancreate