➜

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 loewis
Recipients daniel.urban, debatem1, eric.araujo, exarkun, gdamjan, giampaolo.rodola, gregory.p.smith, heikki, jsamuel, loewis, mcrute, pitrou
Date 2010-06-18.06:19:12
SpamBayes Score 0.005694395
Marked as misclassified No
Message-id <4C1B0FDF.2050909@v.loewis.de>
In-reply-to <AANLkTin6oIbeFNFeOO6q30fFQhMRrrzjb1BjcFKlL1Sn@mail.gmail.com>
Content 
>>   * I'd prefer if the crypto API didn't become OpenSSL specific (like the SSL one is), which would theoretically allow switching in other crypto provider(s).
>
> I agree in theory, although I'm not sure how important this is likely
> to be in practice.

I always wanted to drop OpenSSL from the Windows binaries, and use MS 
CryptoAPI instead.
History
Date User Action Args
2010-06-18 06:19:16loewissetrecipients: + loewis, gregory.p.smith, exarkun, pitrou, giampaolo.rodola, gdamjan, heikki, eric.araujo, debatem1, daniel.urban, mcrute, jsamuel
2010-06-18 06:19:13loewislinkissue8998 messages
2010-06-18 06:19:12loewiscreate