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 rpetrov
Recipients Arfrever, benjamin.peterson, flox, giampaolo.rodola, janssen, pitrou, rpetrov, vstinner
Date 2010-04-10.14:51:55
SpamBayes Score 4.9698085e-10
Marked as misclassified No
Message-id <4BC09088.1070704@roumenpetrov.info>
In-reply-to <1270852621.17.0.261570113194.issue8322@psf.upfronthosting.co.za>
Content
Antoine Pitrou wrote:
>
> Antoine Pitrou<pitrou@free.fr>  added the comment:
>
> After some investigation, the error does occur because of the aforementioned changelog entry (SSLv2 weak ciphers are now disabled by default). To check it I just added the following line to newPySSLObject():
>
>       SSL_CTX_set_cipher_list(self->ctx, "ALL");
>
> Of course this isn't desirable: we shouldn't blindly enable weak ciphers. Instead we could simply add an argument to configure allowed ciphers, and use "ALL" in our tests. Or we could add a separate method to configure ciphers.
>
> (this begs the question of whether this is suitable post-beta1)
>
> What do you think?

List of ciphers is application dependent and configure script can't 
limit users(applications) .

Roumen
History
Date User Action Args
2010-04-10 14:51:57rpetrovsetrecipients: + rpetrov, janssen, pitrou, vstinner, giampaolo.rodola, benjamin.peterson, Arfrever, flox
2010-04-10 14:51:55rpetrovlinkissue8322 messages
2010-04-10 14:51:55rpetrovcreate