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 heikki
Recipients heikki, janssen
Date 2008-09-05.07:05:26
SpamBayes Score 1.0612484e-07
Marked as misclassified No
Message-id <1220598328.06.0.93967704392.issue3597@psf.upfronthosting.co.za>
In-reply-to
Content
Yeah, compatibility can be a problem. The cipher list I used for
M2Crypto was recommended in the book Network Security with OpenSSL (I
think). Besides removing unsafe ciphers, it orders the remaining ciphers
from strongest to weakest, based on the hope/assumption/practice that
peers will hopefully select the first matching cipher. It is not
foolproof, though, so for truly compatible application you'd probably
need to try with different ciphers lists if you run into errors.
However, I have never run into a problem myself with that list, nor has
anyone reported any bugs against M2Crypto because of that.

Defaulting to TLSv1 should select a better cipher list than otherwise,
but I would be a bit concerned about that in turn being an even bigger
compatibility issue. I guess I could ask around.
History
Date User Action Args
2008-09-05 07:05:28heikkisetrecipients: + heikki, janssen
2008-09-05 07:05:28heikkisetmessageid: <1220598328.06.0.93967704392.issue3597@psf.upfronthosting.co.za>
2008-09-05 07:05:27heikkilinkissue3597 messages
2008-09-05 07:05:26heikkicreate