delta/python-packages/pycrypto.git/lib/Crypto/Hash/__init__.py, branch junk/master github.com: dlitz/pycrypto.git Hash: Generic Crypto.Hash.new(algo, [data]) function 2013-02-18T03:18:29+00:00 Dwayne Litzenberger dlitz@dlitz.net 2013-02-17T19:21:35+00:00 0d8ea5ff1607a3d7ae544667bff99229954484ff This allows us to instantiate a new hash given only an existing hash object. 
This allows us to instantiate a new hash given only an existing hash
object.
Hash: Rename SHA->SHA1 and RIPEMD->RIPEMD160 (1/2) 2013-02-17T00:20:23+00:00 Dwayne Litzenberger dlitz@dlitz.net 2013-02-17T00:06:32+00:00 755375bb7d866a01e19153f5809772f4474eb94d These algorithm names were confusing, because there are actually algorithms called "SHA" (a.k.a. SHA-0) and "RIPEMD" (the original version). This commit just renames the modules, with no backward-compatibility support. 
These algorithm names were confusing, because there are actually
algorithms called "SHA" (a.k.a. SHA-0) and "RIPEMD" (the original
version).

This commit just renames the modules, with no backward-compatibility
support.
Added documentation for all hash algorithms 2012-05-05T21:37:19+00:00 Legrandin gooksankoo@hoiptorrow.mailexpire.com 2012-05-05T21:37:19+00:00 2f8a86bd83138bfef618e763fb8b2147f1214af8 (including for HMAC which, strictly speaking, does not belong with them). 
(including for HMAC which, strictly speaking, does not belong with them).
Added Lorenz Quack's native C implementation of all SHA-2 algorithm 2011-10-16T20:41:21+00:00 Legrandin gooksankoo@hoiptorrow.mailexpire.com 2011-10-16T20:41:21+00:00 897b75983c31a9e2630af92161e6206c2480685e (as submitted here https://bugs.launchpad.net/pycrypto/+bug/544792) so that they are available also in Python 2.1, 2.2, 2.3 and 2.4. Regardless where the implementation comes from (Python standard library or our native modules, depending on the Python version), all Crypto.Hash objects are always used as front-ends. 
(as submitted here https://bugs.launchpad.net/pycrypto/+bug/544792)
so that they are available also in Python 2.1, 2.2, 2.3 and 2.4.

Regardless where the implementation comes from (Python standard
library or our native modules, depending on the Python version),
all Crypto.Hash objects are always used as front-ends.
Legal: Add PD dedication to __init__.py files and hash stubs 2009-03-01T15:23:08+00:00 Dwayne C. Litzenberger dlitz@dlitz.net 2009-03-01T01:54:37+00:00 494cad8bc9a706aeb721098e8e1cd19c26d84466 From what I can tell, the authors of these files are: - Andrew Kuchling (who has dedicated his contributions to the public domain); and/or - Dwayne Litzenberger (myself). 
From what I can tell, the authors of these files are:

 - Andrew Kuchling (who has dedicated his contributions to the public domain);
   and/or
 - Dwayne Litzenberger (myself).
cleanup: Move modules to "lib/Crypto" subdirectory. 2009-02-28T18:14:53+00:00 Dwayne C. Litzenberger dlitz@dlitz.net 2009-02-28T18:14:53+00:00 ff8a657a8dd688551c59b4bbf7be33510992ee46 This will avoid the previous situation where scripts like the old "test.py" get included accidentally in a release. It also frees us to put additional build scripts in the top-level directory of the source tree. 
This will avoid the previous situation where scripts like the old "test.py"
get included accidentally in a release.  It also frees us to put additional
build scripts in the top-level directory of the source tree.