[issue8998] add crypto routines to stdlib

[geremy condra]

geremy condra <debatem1 at gmail.com> added the comment:

On Fri, Sep 17, 2010 at 8:55 PM, Gregory P. Smith
<report at bugs.python.org> wrote:
>
> Gregory P. Smith <greg at krypto.org> added the comment:
>
> 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).

I'm open to working with other libraries, but realistically there
isn't a huge point in supporting every crypto library out there, and
it would be a bad idea all around to try. My suggestion would be that
we stick with OpenSSL until a replacement for _ssl.c exists; after
that we can revisit that decision and see where we stand.

Geremy Condra

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue8998>
_______________________________________