delta/python-packages/pycrypto.git - github.com: dlitz/pycrypto.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	Update RIPEMD documentation (deprecated; see RIPEMD160)junk/master	Dwayne Litzenberger	2013-07-14	1	-1/+3
\|
*	Hash: Rename SHA->SHA1 and RIPEMD->RIPEMD160 (2/2)	Dwayne Litzenberger	2013-02-16	1	-0/+24
\| \| \| \| \| \| \| \| \|	These algorithm names were confusing, because there are actually algorithms called "SHA" (a.k.a. SHA-0) and "RIPEMD" (the original version). This commit adds backward-compatibility support for the old Crypto.Hash.SHA and Crypto.Hash.RIPEMD modules.
*	Hash: Rename SHA->SHA1 and RIPEMD->RIPEMD160 (1/2)	Dwayne Litzenberger	2013-02-16	1	-94/+0
\| \| \| \| \| \| \| \| \|	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	Legrandin	2012-05-05	1	-20/+64
\| \| \| \|	(including for HMAC which, strictly speaking, does not belong with them).
*	Merged from upstream (py3k support) and modified so that all unit tests pass.	Legrandin	2011-10-18	1	-2/+3
\|\
* \|	Added Lorenz Quack's native C implementation of all SHA-2 algorithm	Legrandin	2011-10-16	1	-1/+29
\|/ \| \| \| \| \| \| \| \|	(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	Dwayne C. Litzenberger	2009-03-01	1	-0/+20
\| \| \| \| \| \| \| \|	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.	Dwayne C. Litzenberger	2009-02-28	1	-0/+1
	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.