Folks: We needed a few crypto algorithms in our decentralized filesystem project -- the http://allmydata.org "tahoe" project. Our source code is primarily in Python, so I wrote Python wrappers for the crypto algorithms we needed and published the result as a library named "pycryptopp" [1]. I'm very pleased with pycryptopp, and I've been intending to "flesh it out" by adding documentation, more unit tests, wrapping more algorithms, etc., and to announce it to the world in case anyone else wanted to use it.
But, the tahoe project may soon stop using pycryptopp, because we need SSL in addition to separate RSA, DSA, SHA-256, and AES functions. We can probably switch to a Python library named M2Crypto [2] in the future, which is made of SWIG wrappers around OpenSSL, and thus get both our SSL needs and our specific-crypto-algorithm needs satisfied by a single library. Here is the discussion about this issue: [3]. If Crypto++ came with an implementation of SSL then it could be considered as an alternative to M2Crypto. Regards, Zooko [1] http://pypi.python.org/pypi/pycryptopp [2] http://chandlerproject.org/bin/view/Projects/MeTooCrypto [3] http://allmydata.org/trac/tahoe/ticket/11 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [EMAIL PROTECTED] More information about Crypto++ and this group is available at http://www.cryptopp.com. -~----------~----~----~----~------~----~------~--~---
