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 gregory.p.smith
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.00:55:40
SpamBayes Score 5.0385977e-05
Marked as misclassified No
Message-id <1284771346.49.0.906424573776.issue8998@psf.upfronthosting.co.za>
In-reply-to
Content
libtomcrypt is a _great_ library.  That is what hashlib uses for the hash algorithms when OpenSSL is not available.

But the _primary_ reason for using OpenSSL is that it is the defacto open source location for the best architecture specific implementations of any hash and crypto algorithm.  OpenSSL outperforms libtomcrypt by a significant factor (easily 2x) in most cases.

The NSS everywhere effort mentioned in the fedora link sounds interesting.  I support having the ability to link against that instead of OpenSSL or copies of libtomcrypt but I am generally in favor of absolute performance per byte of all algorithms concerned being available.  (ie: don't force hashlib to stop using openssl, just provide an alternative).
History
Date User Action Args
2010-09-18 00:55:47gregory.p.smithsetrecipients: + gregory.p.smith, lemburg, loewis, exarkun, pitrou, vstinner, giampaolo.rodola, gdamjan, lorph, heikki, eric.araujo, debatem1, dmalcolm, daniel.urban, mcrute, jsamuel
2010-09-18 00:55:46gregory.p.smithsetmessageid: <1284771346.49.0.906424573776.issue8998@psf.upfronthosting.co.za>
2010-09-18 00:55:43gregory.p.smithlinkissue8998 messages
2010-09-18 00:55:41gregory.p.smithcreate