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 lorph
Recipients daniel.urban, debatem1, dmalcolm, eric.araujo, exarkun, gdamjan, giampaolo.rodola, gregory.p.smith, heikki, jsamuel, lemburg, loewis, lorph, mcrute, pitrou, vstinner
Date 2010-09-18.22:54:21
SpamBayes Score 4.798939e-05
Marked as misclassified No
Message-id <1284850462.96.0.244805154384.issue8998@psf.upfronthosting.co.za>
In-reply-to
Content
> OpenSSL outperforms libtomcrypt by a significant factor (easily 2x) in most cases.

Gregory, do you have any evidence to substantiate this claim? Not that it isn't plausible, but I couldn't find any benchmarks, and here the author of libtomcrypt finds it to be 40% faster than OpenSSL concerning RSA operations.

http://www.adras.com/TomsFastMath-faster.t71-93.html

>  but I am generally in favor of absolute performance per byte of all algorithms concerned being available

Performance isn't all that matters, or else Python would have used GMP, as Guido discussed here:

http://mail.python.org/pipermail/python-3000/2007-September/010329.html

It is also not a convincing argument that new python libraries should use OpenSSL if possible just because that is what _ssl uses. Compiling Python with OpenSSL support has been optional because it puts additional restrictions on the PSF license. Spreading this restriction to the future crypto module (when we have a choice not to) doesn't make sense.
History
Date User Action Args
2010-09-18 22:54:23lorphsetrecipients: + lorph, lemburg, loewis, gregory.p.smith, exarkun, pitrou, vstinner, giampaolo.rodola, gdamjan, heikki, eric.araujo, debatem1, dmalcolm, daniel.urban, mcrute, jsamuel
2010-09-18 22:54:22lorphsetmessageid: <1284850462.96.0.244805154384.issue8998@psf.upfronthosting.co.za>
2010-09-18 22:54:21lorphlinkissue8998 messages
2010-09-18 22:54:21lorphcreate