delta/python-packages/pycrypto.git/lib/Crypto/SelfTest/Hash/test_MD2.py, branch master

Added support for PKCS#8-encrypted private keys.

2013-07-15T04:16:46+00:00

The patch contains the following changes:

- Private RSA keys can be imported/exported in encrypted form,
  protected according to PKCS#8 and:

  * PBKDF2WithHMAC-SHA1AndDES-EDE3-CBC.
  * PBKDF2WithHMAC-SHA1AndAES128-CBC
  * PBKDF2WithHMAC-SHA1AndAES192-CBC
  * PBKDF2WithHMAC-SHA1AndAES256-CBC

  In addition to that, it is possible to import keys i the
  following weak formats:

  * pbeWithMD5AndDES-CBC
  * pbeWithSHA1AndRC2-CBC
  * pbeWithMD5AndRC2-CBC
  * pbeWithSHA1AndDES-CBC

- The following new module (and 1 new package) are added:

  * Crypto.Util.Padding for simple padding/unpadding logic
  * Crypto.IO._PBES for PBE-related PKCS#5 logic
  * Crypto.IO.PEM for PEM wrapping/unwrapping
  * Crypto.IO.PKCS8 for PKCS#8 wrapping/unwrapping

- All Object ID (OIDs) are now in dotted form to increase
  readability.

- Add AES support to PEM format (decode only).
  The PEM module can decrypt messages protected with AES-CBC.

- Update RSA import test cases.

- Updated to PKCS8 test cases

Merged from upstream (py3k support) and modified so that all unit tests pass.

2011-10-18T21:20:26+00:00

Added Lorenz Quack's native C implementation of all SHA-2 algorithm

2011-10-16T20:41:21+00:00

(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.

Unwraping byte conversion on test vectors.

2011-04-24T15:35:12+00:00

Doing the wraping later, at the point of use instead.

Add test routines to validate OID in hash algorithms.

2011-02-03T00:35:58+00:00

Changes to allow pycrpyto to work on Python 3.x as well as 2.1 through 2.7

2010-12-28T21:26:52+00:00

Legal: Dedicate my files to the public domain.

2009-03-01T15:22:51+00:00

In an attempt to simplify the copyright status of PyCrypto, I'm placing my
code into the public domain, and encouraging other contributors to do the
same.

I have used a public domain dedication that was recommended in a book on FOSS legal
issues[1], followed by the warranty disclaimer boilerplate from the MIT license.

[1] _Intellectual Property and Open Source: A Practical Guide to Protecting
    Code_, a book written by Van Lindberg and published by O'Reilly Media.
    (ISBN 978-0-596-51796-0)

cleanup: Move modules to "lib/Crypto" subdirectory.

2009-02-28T18:14:53+00:00

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.