Should we move up to this new version? Regards, Tim
-------- Original Message -------- Subject: [announce-crypto] Bouncy Castle Crypto Provider Package version 1.32 now available Date: Wed, 29 Mar 2006 12:56:18 +1100 From: Jon Eaves <[EMAIL PROTECTED]> To: dev-crypto <[EMAIL PROTECTED]>, [EMAIL PROTECTED], [EMAIL PROTECTED], KVM Interest <[EMAIL PROTECTED]> Hi all, The latest relase of BC is now ready after a couple of false starts in the beta process. Thanks always to our tireless reporters of issues, one day maybe all vendors will create certificates in the same way. New features in this release include support for elliptic curves over F2m, suport for ECDSA with CMS and S/MIME, and support for a wider range of PSS signature types in CRL and certificate verification. In addition further work has been done on improving path validation compliance with RFC 3280, OpenPGP text signatures now work correctly in environments with '\r' as a line separator, a typo in the header for OpenPGP clear text SHA256 signatures has been fixed, several encoding compatability issue with the streaming CMS and S/MIME APIs have been fixed and it should now be possible to stop the S/MIME parsers from leaving temporary files around in all operating system environments. As usual, the latest releases can be found at : http://www.bouncycastle.org/ And for those who like living on the bleeding edge, the betas can be downloaded from: http://www.bouncycastle.org/betas/ Please note, make sure that beta feedback is sent to the [EMAIL PROTECTED] address, and not the general mailing list (dev-crypto) -- Jon Eaves <[EMAIL PROTECTED]> http://www.eaves.org/blog/ Co-Author of "Apache Tomcat Bible", "Professional Tomcat 5", "Beginning JavaServer Pages" -- Tim Ellison ([EMAIL PROTECTED]) IBM Java technology centre, UK.
