ANN: PyCrypto 2.1.0 alpha 2 released

--EVF5PPMfhYS0aIcm
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

PyCrypto 2.1.0alpha2 has been released.  I'm going to push through a stable=
=20
release as soon as I can, since at this point I think all the major issues=
=20
have been resolved[*], and it's getting a bit ridiculous that it's taking=
=20
me longer to release a stable PyCrypto than it takes to release a stable=20
Debian.

You can get this alpha release via HTTP at:

   http://ftp.dlitz.net/pub/dlitz/crypto/pycrypto/pycrypto-2.1.0a2.tar.gz
   http://ftp.dlitz.net/pub/dlitz/crypto/pycrypto/pycrypto-2.1.0a2.tar.gz.a=
sc

You can also get it from the git repository:

   $ git clone git://git.pycrypto.org:9419/crypto/pycrypto-2.x.git
   $ cd pycrypto-2.x
   $ git checkout v2.1.0alpha2

The ChangeLog is available online at:

   http://gitweb.pycrypto.org/?p=3Dcrypto/pycrypto-2.x.git;a=3Dblob;f=3DCha=
ngeLog;h=3D94731b70962732ea718e63bfdf21c3722ee94af4;hb=3Da7748d0e65fe17fbcb=
20f7b086536c3ccf68de43

Please test it and post your experiences to the PyCrypto mailing list:

   [email protected]

and/or file bug reports on Launchpad:

   https://bugs.launchpad.net/pycrypto

There has been a huge number of changes since the last stable release[**],=
=20
and not a lot of feedback so far, so I would really appreciate any feedback=
=20
even if it's just a simple oneliner like, "built on <OS> <ARCHITECTURE>;=20
used with <PROGRAM>; works fine."

The files for this release have the following SHA256 sums:

bc42f57eae5bf1ef4319e6e99cd45281b096d0de9ae4f00a0b6fa7ffa359b349 *pycrypto-=
2.1.0a2.tar.gz
f2c821e10d5d473af153fb82fd87101772aaf5583aea40e0bac0cb6b586d2c7c *pycrypto-=
2.1.0a2.tar.gz.asc

Cheers,
- Dwayne

--=20
Dwayne C. Litzenberger <[email protected]>
  Key-signing key   - 19E1 1FE8 B3CF F273 ED17  4A24 928C EC13 39C2 5CF7
  Annual key (2009) - C805 1746 397B 0202 2758  2821 58E0 894B 81D2 582E

[*] ... with the possible exception of RSA key generation, which some=20
people have suggested might be inadequate.  I could use some help with=20
this.  See https://bugs.launchpad.net/pycrypto/+bug/408660

[**] "git diff -C --shortstat v2.0.1 v2.1.0alpha2" shows:
 178 files changed, 20306 insertions(+), 7336 deletions(-)

--EVF5PPMfhYS0aIcm
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iFYEAREKAAYFAkrb+eUACgkQWOCJS4HSWC7VXQDfZMhoPlTd6xI01uVoYX+/xeBR
ic5zXCV3rYUAWADeKPgC4Sk7ZptB7Br8Pjeg1tw6TXynI8FdskyE8A==
=OiS5
-----END PGP SIGNATURE-----

--EVF5PPMfhYS0aIcm--