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 pitrou
Recipients Arfrever, giampaolo.rodola, janssen, loewis, pitrou
Date 2010-05-05.18:52:41
SpamBayes Score 8.6087075e-06
Marked as misclassified No
Message-id <1273085706.3499.6.camel@localhost.localdomain>
In-reply-to <1273085110.02.0.138757082812.issue8629@psf.upfronthosting.co.za>
Content
> I don't think we should use the openssl binary for anything. It may
> belong to a different version, and it may not be available (in
> particular on Windows).

Agreed.

> I don't understand the problem you are trying to solve. What exactly
> is it that will stop working on OpenSSL 1.0?

OpenSSL 1.0.0 disables SSLv2 by default, which means the protocol
combination tests give different results (for example, an SSLv23 client
will refuse talking to an SSLv2 server, because the client will attempt
an SSLv3 hello).

We need therefore to fix these tests, by differentiating their outcomes
depending on the OpenSSL version.

(trunk and py3k use a different approach: they manually enable SSLv2
ciphers in those tests, using the new "ciphers" argument, which makes
the behaviour consistent accross all OpenSSL versions)
History
Date User Action Args
2010-05-05 18:52:42pitrousetrecipients: + pitrou, loewis, janssen, giampaolo.rodola, Arfrever
2010-05-05 18:52:41pitroulinkissue8629 messages
2010-05-05 18:52:41pitroucreate