update

1 files changed, 172 insertions, 162 deletions

diff --git a/docs/releasenotes.html b/docs/releasenotes.html
index b5bfa81e..e282acba 100644
--- a/docs/releasenotes.html
+++ b/docs/releasenotes.html
@@ -23,9 +23,19 @@ to conform the algorithms to the JCE framework.
 <h2>2.0 Release History</h2>
 
 <h3>2.1.1 Version</h3>
-Release 1.50
+Release 1.51
 <h3>2.1.2 Defects Fixed</h3>
 <ul>
+<li>The AEAD GCM AlgorithmParameters object was unable to return a GCMParameterSpec object. This has been fixed.</li>
+</ul>
+<h3>2.1.3 Additional Features and Functionality</h3>
+<ul>
+<li>The range of key algorithm names that will be interpreted by KeyAgreement.generateSecret() has been expanded for ECDH derived algorithms in the provider. A KeyAgreement of ECDHwithSHA1KDF can now be explicitly created.</li>
+</ul>
+<h3>2.2.1 Version</h3>
+Release 1.50
+<h3>2.2.2 Defects Fixed</h3>
+<ul>
 <li>The DualECSP800DRBG sometimes truncated the last block in the generated stream incorrectly. This has been fixed.</li>
 <li>Keys produced from RSA certificates with specialised parameters would lose the parameter settings. This has been fixed.</li>
 <li>OAEP parameters were being ignored on CMS key trans recipient processing. This has been fixed.</li>
@@ -38,7 +48,7 @@ Release 1.50
 <li>Default RC2 parameters for 40 bit RC2 keys in CMSEnvelopedData were encoding incorrectly. This has been fixed.</li>
 <li>In case of a long hash the DSTU4145 implementation would sometimes remove one bit too much during truncation. This has been fixed.</li>
 </ul>
-<h3>2.1.3 Additional Features and Functionality</h3>
+<h3>2.2.3 Additional Features and Functionality</h3>
 <ul>
 <li>Additional work has been done on CMS recipient generation to simplify the generation of OAEP encrypted messages and allow for non-default parameters.</li>
 <li>OCB implementation updated to account for changes in draft-irtf-cfrg-ocb-03.</li>
@@ -57,7 +67,7 @@ Release 1.50
 <li>Package version information is now included in the jar MANIFEST.MF.</li>
 <li>The JDK 1.5+ provider will now recognise and use GCMParameterSpec if it is run in a 1.7 JVM.</li>
 </ul>
-<h3>2.1.4 Notes</h3>
+<h3>2.2.4 Notes</h3>
 <ul>
 <li>org.bouncycastle.crypto.DerivationFunction is now a base interface, the getDigest() method appears on DigestDerivationFunction.</li>
 <li>Recent developments at NIST indicate the SHA-3 may be changed before final standardisation. Please bare this in mind if you are using it.</li>
@@ -67,9 +77,9 @@ Release 1.50
 <li>ECDH support for OpenPGP should still be regarded as experimental. It is still possible there will be compliance issues with other implementations.</li>
 </ul>
 
-<h3>2.2.1 Version</h3>
+<h3>2.3.1 Version</h3>
 Release 1.49
-<h3>2.2.2 Defects Fixed</h3>
+<h3>2.3.2 Defects Fixed</h3>
 <ul>
 <li>Occasional ArrayOutOfBounds exception in DSTU-4145 signature generation has been fixed.</li>
 <li>The handling of escaped characters in X500 names is much improved.</li>
@@ -80,7 +90,7 @@ Release 1.49
 <li>PEMParser would throw a NullPointerException if it ran into explicit EC curve parameters, it would also throw an Exception if the named curve was not already defined. The parser now returns X9ECParmameters for explicit parameters and returns an ASN1ObjectIdentifier for a named curve.</li>
 <li>The V2TBSCertListGenerator was adding the wrong date type for CRL invalidity date extensions. This has been fixed.</li>
 </ul>
-<h3>2.2.3 Additional Features and Functionality</h3>
+<h3>2.3.3 Additional Features and Functionality</h3>
 <ul>
 <li>A SecretKeyFactory has been added that enables use of PBKDF2WithHmacSHA.</li>
 <li>Support has been added to PKCS12 KeyStores and PfxPdu to handle PKCS#5 encrypted private keys.</li>
@@ -109,15 +119,15 @@ class NonMemoableDigest has been added which hides the Memoable interface where
 <li>A basic commitment package has been introduced into the lightweight API containing a digest based commitment scheme.</li>
 <li>It is now possible to set the NotAfter and NotBefore date in the CRMF CertificateRequestMessageBuilder class.</li>
 </ul>
-<h3>2.2.4 Notes</h3>
+<h3>2.3.4 Notes</h3>
 <ul>
 <li>The NTRU implementation has been moved into the org.bouncycastle.pqc package hierarchy.</li>
 <li>The change to PEMParser to support explicit EC curves is not backward compatible. If you run into a named curve you need to use org.bouncycastle.asn1.x9.ECNamedCurveTable.getByOID() to look the curve up if required.</li>
 </ul>
 
-<h3>2.3.1 Version</h3>
+<h3>2.4.1 Version</h3>
 Release 1.48
-<h3>2.3.2 Defects Fixed</h3>
+<h3>2.4.2 Defects Fixed</h3>
 <ul>
 <li>Occasional key compatibility issues in IES due to variable length keys have been fixed.</li>
 <li>PEMWriter now recognises the new PKCS10CertificationRequest object.</li>
@@ -129,7 +139,7 @@ Release 1.48
 <li>A regression in 1.47 which prevented key wrapping with regular symmetric PBE algorihtms has been fixed.</li>
 </ul>
 
-<h3>2.3.3 Additional Features and Functionality</h3>
+<h3>2.4.3 Additional Features and Functionality</h3>
 <ul>
 <li>IES now supports auto generation of ephemeral keys in both the JCE and the lightweight APIs.</li>
 <li>A new class PEMParser has been added to return the new CertificateHolder and Request objects introduced recently.</li>
@@ -144,9 +154,9 @@ Release 1.48
 <li>T61String now uses UTF-8 encoding by default rather than a simple 8 bit transform.</li>
 </ul>
 
-<h3>2.4.1 Version</h3>
+<h3>2.5.1 Version</h3>
 Release 1.47
-<h3>2.4.2 Defects Fixed</h3>
+<h3>2.5.2 Defects Fixed</h3>
 <ul>
 <li>OpenPGP ID based certifications now support UTF-8. Note: this may mean that some old certifications no longer validate - if this happens a retry can be added using by converting the ID using Strings.fromByteArray(Strings.toByteArray(id)) - this will strip out the top byte in each character.</li>
 <li>IPv4/IPv6 parsing in CIDR no longer assumes octet boundaries on a mask.</li>
@@ -163,7 +173,7 @@ Release 1.47
 <li>Check of DH parameter L could reject some valid keys. This is now fixed.</li>
 </ul>
 
-<h3>2.4.3 Additional Features and Functionality</h3>
+<h3>2.5.3 Additional Features and Functionality</h3>
 <ul>
 <li>Support is now provided via the RepeatedKey class to enable IV only re-initialisation in the JCE layer. The same effect can be acheived in the light weight API by using null as the key parameter when creating a ParametersWithIV object.</li>
 <li>CRMF now supports empty poposkInput.</li>
@@ -183,14 +193,14 @@ Release 1.47
 <li>The J2ME lcrypto release now includes higher level classes for handling PKCS, CMS, CRMF, CMP, EAC, OpenPGP, and certificate generation.</li>
 </ul>
 
-<h3>2.4.4 Other notes</h3>
+<h3>2.5.4 Other notes</h3>
 <p>
 Okay, so we have had to do another release. The issue we have run into is that we probably didn't go far enough in 1.46, but we are now confident that moving from this release to 2.0 should be largely just getting rid of deprecated methods. While this release does change a lot it is relatively straight forward to do a port and we have a <a href="http://www.bouncycastle.org/wiki/display/JA1/Porting+from+earlier+BC+releases+to+1.47+and+later">porting guide</a> which explains the important ones. The area there has been the most change in is the ASN.1 library which was in bad need of a rewrite after 10 years of patching. On the bright side the rewrite did allow us to eliminate a few problems and bugs in the ASN.1 library, so we have some hope anyone porting to it will also have similar benefits. As with 1.46 the other point of emphasis has been making sure interface support is available for operations across the major APIs, so the lightweight API or some local role your own methods can be used instead for doing encryption and signing.
 </p>
 
-<h3>2.5.1 Version</h3>
+<h3>2.6.1 Version</h3>
 Release 1.46
-<h3>2.5.2 Defects Fixed</h3>
+<h3>2.6.2 Defects Fixed</h3>
 <ul>
 <li>An edge condition in ECDSA which could result in an invalid signature has been fixed.</li>
 <li>Exhaustive testing has been performed on the ASN.1 parser, eliminating another potential OutOfMemoryException and several escaping run time exceptions.</li>
@@ -199,7 +209,7 @@ Release 1.46
 <li>DERGeneralizedTime.getDate() would produce incorrect results for fractional seconds. This has been fixed.</li>
 <li>PSSSigner would produce incorrect results if the MGF digest and content digest were not the same. This has been fixed.</li>
 </ul>
-<h3>2.5.3 Additional Features and Functionality</h3>
+<h3>2.6.3 Additional Features and Functionality</h3>
 <ul>
 <li>A null genTime can be passed to TimeStampResponseGenerator.generate() to generate timeNotAvailable error responses.</li>
 <li>Support has been added for reading and writing of openssl PKCS#8 encrypted keys.</li>
@@ -216,7 +226,7 @@ Release 1.46
 <li>PGP public subkeys can now be separately decoded and encoded.</li>
 <li>An IV can now be passed to an ISO9797Alg3Mac.</li>
 </ul>
-<h3>2.5.4 Other notes</h3>
+<h3>2.6.4 Other notes</h3>
 <p>
 Baring security patches we expect 1.46 will be the last of the 1.* releases. The next release of
 BC will be version 2.0. For this reason a lot of things in 1.46 that relate to CMS have been deprecated and
@@ -234,27 +244,27 @@ So there are four things useful to know about this release:
 <li>The org.bouncycastle.cms.RecipientId class now has a collection of subclasses to allow for more specific recipient matching. If you are creating your own recipient ids you should use the constructors for the subclasses rather than relying on the set methods inherited from X509CertSelector. The dependencies on X509CertSelector and CertStore will be removed from the version 2 CMS API.</li>
 </ul>
 </p>
-<h3>2.6.1 Version</h3>
+<h3>2.7.1 Version</h3>
 Release 1.45
-<h3>2.6.2 Defects Fixed</h3>
+<h3>2.7.2 Defects Fixed</h3>
 <ul>
 <li>OpenPGP now supports UTF-8 in file names for literal data.</li>
 <li>The ASN.1 library was losing track of the stream limit in a couple of places, leading to the potential of an OutOfMemoryError on a badly corrupted stream. This has been fixed.</li>
 <li>The provider now uses a privileged block for initialisation.</li>
 <li>JCE/JCA EC keys are now serialisable.</li>
 </ul>
-<h3>2.6.3 Additional Features and Functionality</h3>
+<h3>2.7.3 Additional Features and Functionality</h3>
 <ul>
 <li>Support for EC MQV has been added to the light weight API, provider, and the CMS/SMIME library.</li>
 </ul>
-<h3>2.6.4 Security Advisory</h3>
+<h3>2.7.4 Security Advisory</h3>
 <ul>
 <li>This version of the provider has been specifically reviewed to eliminate possible timing attacks on algorithms such as GCM and CCM mode.</li>
 </ul>
 
-<h3>2.7.1 Version</h3>
+<h3>2.8.1 Version</h3>
 Release 1.44
-<h3>2.7.2 Defects Fixed</h3>
+<h3>2.8.2 Defects Fixed</h3>
 <ul>
 <li>The reset() method in BufferedAsymmetricBlockCipher is now fully clearing the buffer.</li>
 <li>Use of ImplicitlyCA with KeyFactory and Sun keyspec no longer causes NullPointerException.</li>
@@ -270,7 +280,7 @@ Release 1.44
 <li>PKIXCertPathReviewer.getTrustAnchor() could occasionally cause a null pointer exception or an exception due to conflicting trust anchors. This has been fixed.</li>
 <li>Handling of explicit CommandMap objects with the generation of S/MIME messages has been improved.</li>
 </ul>
-<h3>2.7.3 Additional Features and Functionality</h3>
+<h3>2.8.3 Additional Features and Functionality</h3>
 <ul>
 <li>PEMReader/PEMWriter now support encrypted EC keys.</li>
 <li>BC generated EC private keys now include optional fields required by OpenSSL.</li>
@@ -286,22 +296,22 @@ Release 1.44
 <li>Support for raw signatures has been extended to RSA and RSA-PSS in the provider. RSA support can be used in CMSSignedDataStreamGenerator to support signatures without signed attributes.</li>
 </ul>
 
-<h3>2.8.1 Version</h3>
+<h3>2.9.1 Version</h3>
 Release 1.43
-<h3>2.8.2 Defects Fixed</h3>
+<h3>2.9.2 Defects Fixed</h3>
 <ul>
 <li>Multiple countersignature attributes are now correctly collected.</li>
 <li>Two bugs in HC-128 and HC-256 related to sign extension and byte swapping have been fixed. The implementations now pass the latest ecrypt vector tests.</li>
 <li>X509Name.hashCode() is now consistent with equals.</li>
 </ul>
-<h3>2.8.3 Security Advisory</h3>
+<h3>2.9.3 Security Advisory</h3>
 <ul>
 <li>The effect of the sign extension bug was to decrease the key space the HC-128 and HC-256 ciphers were operating in and the byte swapping inverted every 32 bits of the generated stream. If you are using either HC-128 or HC-256 you must upgrade to this release.</li>
 </ul>
 
-<h3>2.9.1 Version</h3>
+<h3>2.10.1 Version</h3>
 Release 1.42
-<h3>2.9.2 Defects Fixed</h3>
+<h3>2.10.2 Defects Fixed</h3>
 <ul>
 <li>A NullPointer exception which could be result from generating a diffie-hellman key has been fixed.</li>
 <li>CertPath validation could occasionally mistakenly identify a delta CRL. This has been fixed.</li>
@@ -314,7 +324,7 @@ Release 1.42
 <li>Multiplication by negative powers of two is fixed in BigInteger.</li>
 <li>OptionalValidity now encodes correctly.</li>
 </ul>
-<h3>2.9.3 Additional Features and Functionality</h3>
+<h3>2.10.3 Additional Features and Functionality</h3>
 <ul>
 <li>Support for NONEwithECDSA has been added.</li>
 <li>Support for Grainv1 and Grain128 has been added.</li>
@@ -325,9 +335,9 @@ Release 1.42
 <li>Support for the SRP-6a protocol has been added to the lightweight API.</li>
 </ul>
 
-<h3>2.10.1 Version</h3>
+<h3>2.11.1 Version</h3>
 Release 1.41
-<h3>2.10.2 Defects Fixed</h3>
+<h3>2.11.2 Defects Fixed</h3>
 <ul>
 <li>The GeneralName String constructor now supports IPv4 and IPv6 address parsing.</li>
 <li>An issue with nested-multiparts with postamble for S/MIME that was causing signatures to fail verification has been fixed.</li>
@@ -338,7 +348,7 @@ Release 1.41
 <li>Standard name "DiffieHellman" is now supported in the provider.</li>
 <li>Better support for equality tests for '#' encoded entries has been added to X509Name.</li>
 </ul>
-<h3>2.10.3 Additional Features and Functionality</h3>
+<h3>2.11.3 Additional Features and Functionality</h3>
 <ul>
 <li>Camellia is now 12.5% faster than previously.</li>
 <li>A smaller version (around 8k compiled) of Camellia, CamelliaLightEngine has also been added.</li>
@@ -349,9 +359,9 @@ Release 1.41
 <li>Support for reading and extracting personalised certificates in PGP Secret Key rings has been added.</li>
 </ul>
 
-<h3>2.11.1 Version</h3>
+<h3>2.12.1 Version</h3>
 Release 1.40
-<h3>2.11.2 Defects Fixed</h3>
+<h3>2.12.2 Defects Fixed</h3>
 <ul>
 <li>EAX mode ciphers were not resetting correctly after a doFinal/reset. This has been fixed.</li>
 <li>The SMIME API was failing to verify doubly nested multipart objects in signatures correctly. This has been fixed.</li>
@@ -367,7 +377,7 @@ Release 1.40
 <li>The '+' character can now be escaped or quoted in the constructor for X509Name, X509Prinicipal.</li>
 <li>Fix to regression from 1.38: PKIXCertPathValidatorResult.getPublicKey was returning the wrong public key when the BC certificate path validator was used.</li>
 </ul>
-<h3>2.11.3 Additional Features and Functionality</h3>
+<h3>2.12.3 Additional Features and Functionality</h3>
 <ul>
 <li>Galois/Counter Mode (GCM) has been added to the lightweight API and the JCE provider.</li>
 <li>SignedPublicKeyAndChallenge and PKCS10CertificationRequest can now take null providers if you need to fall back to the default provider mechanism.</li>
@@ -375,14 +385,14 @@ Release 1.40
 <li>Unnecessary local ID attributes on certificates in PKCS12 files are now automatically removed.</li>
 <li>The PKCS12 store types PKCS12-3DES-3DES and PKCS12-DEF-3DES-3DES have been added to support generation of PKCS12 files with both certificates and keys protected by 3DES.</li>
 </ul>
-<h3>2.11.4 Additional Notes</h3>
+<h3>2.12.4 Additional Notes</h3>
 <ul>
 <li>Due to problems for some users caused by the presence of the IDEA algorithm, an implementation is no longer included in the default signed jars. Only the providers of the form bcprov-ext-*-*.jar now include IDEA.</li>
 </ul>
 
-<h3>2.12.1 Version</h3>
+<h3>2.13.1 Version</h3>
 Release 1.39
-<h3>2.12.2 Defects Fixed</h3>
+<h3>2.13.2 Defects Fixed</h3>
 <ul>
 <li>A bug causing the odd NullPointerException has been removed from the LocalizedMessage class.</li>
 <li>IV handling in CMS for the SEED and Camellia was incorrect. This has been fixed.</li>
@@ -396,7 +406,7 @@ Release 1.39
 <li>A decoding issue with a mis-identified tagged object in CertRepMessage has been fixed.</li>
 <li>\# is now properly recognised in the X509Name class.</li>
 </ul>
-<h3>2.10.3 Additional Features and Functionality</h3>
+<h3>2.13.3 Additional Features and Functionality</h3>
 <ul>
 <li>Certifications associated with user attributes can now be created, verified and removed in OpenPGP.</li>
 <li>API support now exists for CMS countersignature reading and production.</li>
@@ -410,9 +420,9 @@ Release 1.39
 <li>The ProofOfPossession class now better supports the underlying ASN.1 structure.</li>
 <li>Support has been added to the provider for the VMPC MAC.</li>
 </ul>
-<h3>2.13.1 Version</h3>
+<h3>2.14.1 Version</h3>
 Release 1.38
-<h3>2.13.2 Defects Fixed</h3>
+<h3>2.14.2 Defects Fixed</h3>
 <ul>
 <li>SMIME signatures containing non-standard quote-printable data could be altered by SMIME encryption. This has been fixed.</li>
 <li>CMS signatures that do not use signed attributes were vulnerable to one of Bleichenbacher's RSA signature forgery attacks. This has been fixed.</li>
@@ -426,7 +436,7 @@ Release 1.38
 <li>Overwriting entities in a PKCS#12 file was not fully compliant with the JavaDoc for KeyStore. This has been fixed.</li>
 <li>TlsInputStream.read() could appear to return end of file when end of file had not been reached. This has been fixed.</li>
 </ul>
-<h3>2.13.3 Additional Features and Functionality</h3>
+<h3>2.14.3 Additional Features and Functionality</h3>
 <ul>
 <li>Buffering in the streaming CMS has been reworked. Throughput is now usually higher and the behaviour is more predictable.</li>
 <li>It's now possible to pass a table of hashes to a CMS detached signature rather than having to always pass the data.</li>
@@ -437,9 +447,9 @@ Release 1.38
 <li>CertPathReviewer has better handling for problem trust anchors.</li>
 <li>Base64 encoder now does initial size calculations to try to improve resource usage.</li>
 </ul>
-<h3>2.14.1 Version</h3>
+<h3>2.15.1 Version</h3>
 Release 1.37
-<h3>2.14.2 Defects Fixed</h3>
+<h3>2.15.2 Defects Fixed</h3>
 <ul>
 <li>The ClearSignedFileProcessor example for OpenPGP did not take into account trailing white space in
 the file to be signed. This has been fixed.</li>
@@ -453,7 +463,7 @@ the file to be signed. This has been fixed.</li>
 <li>The default private key length in the lightweght API for generated DiffieHellman parameters was absurdly small, this has been fixed.</li>
 <li>Cipher.getParameters() for PBEwithSHAAndTwofish-CBC was returning null after intialisation. This has been fixed.</li>
 </ul>
-<h3>2.14.3 Additional Features and Functionality</h3>
+<h3>2.15.3 Additional Features and Functionality</h3>
 <ul>
 <li>The block cipher mode CCM has been added to the provider and light weight API.</li>
 <li>The block cipher mode EAX has been added to the provider and light weight API.</li>
@@ -472,9 +482,9 @@ the file to be signed. This has been fixed.</li>
 <li>The JCE provider now supports RIPEMD160withECDSA.</li>
 </ul>
 
-<h3>2.15.1 Version</h3>
+<h3>2.16.1 Version</h3>
 Release 1.36
-<h3>2.15.2 Defects Fixed</h3>
+<h3>2.16.2 Defects Fixed</h3>
 <ul>
 <li>DSA key generator now checks range and keysize.</li>
 <li>Class loader issues with i18n classes should now be fixed.</li>
@@ -488,7 +498,7 @@ regression for processing some messages with embedded multiparts that contained
 <li>Some surrogate pairs were not assembled correctly by the UTF8 decoder. This has been fixed.</li>
 <li>Alias resolution in PKCS#12 is now case insensitive.</li>
 </ul>
-<h3>2.15.3 Additional Features and Functionality</h3>
+<h3>2.16.3 Additional Features and Functionality</h3>
 <ul>
 <li>CMS/SMIME now supports basic EC KeyAgreement with X9.63.</li>
 <li>CMS/SMIME now supports RFC 3211 password based encryption.</li>
@@ -504,9 +514,9 @@ regression for processing some messages with embedded multiparts that contained
 <li>DSASigner now handles long messages. SHA2 family digest support for DSA has been added to the provider.</li>
 </ul>
 
-<h3>2.16.1 Version</h3>
+<h3>2.17.1 Version</h3>
 Release 1.35
-<h3>2.16.2 Defects Fixed</h3>
+<h3>2.17.2 Defects Fixed</h3>
 <ul>
 <li>Test data files are no longer in the provider jars.</li>
 <li>SMIMESignedParser now handles indefinite length data in SignerInfos.</li>
@@ -521,7 +531,7 @@ Release 1.35
 <li>The IESEngine could incorrectly encrypt data when used in block cipher mode. This has been fixed.
 <li>An error in the encoding of the KEKRecipientInfo has been fixed. Compatability warning: this may mean that versions of BC mail prior to 1.35 will have trouble processing KEK messages produced by 1.35 or later.
 </ul>
-<h3>2.16.3 Additional Features and Functionality</h3>
+<h3>2.17.3 Additional Features and Functionality</h3>
 <ul>
 <li>Further optimisations to elliptic curve math libraries.</li>
 <li>API now incorporates a CertStore which should be suitable for use with LDAP.</li>
@@ -542,9 +552,9 @@ Release 1.35
 <li>PEMReader now supports OpenSSL ECDSA key pairs.</li>
 <li>PGP packet streams can now be closed off using close() on the returned stream as well as closing the generator.</li>
 </ul>
-<h3>2.17.1 Version</h3>
+<h3>2.18.1 Version</h3>
 Release 1.34
-<h3>2.17.2 Defects Fixed</h3>
+<h3>2.18.2 Defects Fixed</h3>
 <ul>
 <li>Endianess of integer conversion in KDF2BytesGenerator was incorrect. This has been fixed.
 <li>Generating critical signature subpackets in OpenPGP would result in a zero packet tag. This has been fixed.
@@ -556,7 +566,7 @@ Bleichenbacher's RSA signature forgery attack. This has been fixed.
 <li>PGP Identity strings were only being interpreted as ASCII rather than UTF8. This has been fixed.
 <li>CertificateFactory.generateCRLs now returns a Collection rather than null.
 </ul>
-<h3>2.17.3 Additional Features and Functionality</h3>
+<h3>2.18.3 Additional Features and Functionality</h3>
 <ul>
 <li>An ISO18033KDFParameters class had been added to support ISO18033 KDF generators.
 <li>An implemention of the KDF1 bytes generator algorithm has been added.
@@ -576,14 +586,14 @@ The build scripts now run this target by default.
 <li>Performance of the prime number generation in the BigInteger library has been further improved.
 <li>In line with RFC 3280 section 4.1.2.4 DN's are now encoded using UTF8String by default rather than PrintableString.
 </ul>
-<h3>2.17.5 Security Advisory</h3>
+<h3>2.18.5 Security Advisory</h3>
 <ul>
 <li>If you are using public exponents with the value three you *must* upgrade to this release, otherwise it
 will be possible for attackers to exploit some of Bleichenbacher's RSA signature forgery attacks on your applications.</li>
 </ul>
-<h3>2.18.1 Version</h3>
+<h3>2.19.1 Version</h3>
 Release 1.33
-<h3>2.18.2 Defects Fixed</h3>
+<h3>2.19.2 Defects Fixed</h3>
 <ul>
 <li>OCSPResponseData was including the default version in its encoding. This has been fixed.
 <li>BasicOCSPResp.getVersion() would throw a NullPointer exception if called on a default version response. This has been fixed.
@@ -592,7 +602,7 @@ Release 1.33
 <li>ArmoredInputStream was not closing the underlying stream on close. This has been fixed.
 <li>Small base64 encoded strings with embedded white space could decode incorrectly using the Base64 class. This has been fixed.
 </ul>
-<h3>2.18.3 Additional Features and Functionality</h3>
+<h3>2.19.3 Additional Features and Functionality</h3>
 <ul>
 <li>The X509V2CRLGenerator now supports adding general extensions to CRL entries.
 <li>A RoleSyntax implementation has been added to the x509 ASN.1 package, and the AttributeCertificateHolder class now support the IssuerSerial option.
@@ -600,9 +610,9 @@ Release 1.33
 <li>DERUTF8String now supports surrogate pairs.
 </ul>
 
-<h3>2.19.1 Version</h3>
+<h3>2.20.1 Version</h3>
 Release 1.32
-<h3>2.19.2 Defects Fixed</h3>
+<h3>2.20.2 Defects Fixed</h3>
 <ul>
 <li>Further work has been done on RFC 3280 compliance.
 <li>The ASN1Sequence constructor for SemanticsInformation would sometimes throw a ClassCastException on reconstruction an object from a byte stream. This has been fixed.
@@ -619,7 +629,7 @@ which has a dispose method on it which should allow removal of the file backing
 <li>OpenPGP clear text signatures containing '\r' as line separators were not being correctly canonicalized. This has been fixed.
 </ul>
 
-<h3>2.19.3 Additional Features and Functionality</h3>
+<h3>2.20.3 Additional Features and Functionality</h3>
 <ul>
 <li>The ASN.1 library now includes classes for the ICAO Electronic Passport.
 <li>Support has been added to CMS and S/MIME for ECDSA.
@@ -628,15 +638,15 @@ which has a dispose method on it which should allow removal of the file backing
 <li>Support has been added for repeated attributes in CMS and S/MIME messages.
 <li>A wider range of RSA-PSS signature types is now supported for CRL and Certificate verification.
 </ul>
-<h3>2.19.4 Possible compatibility issue</h3>
+<h3>2.20.4 Possible compatibility issue</h3>
 <ul>
 <li>Previously elliptic curve keys and points were generated with point compression enabled by default.
 Owing to patent issues in some jurisdictions, they are now generated with point compression disabled by default.
 </ul>
 
-<h3>2.20.1 Version</h3>
+<h3>2.21.1 Version</h3>
 Release 1.31
-<h3>2.20.2 Defects Fixed</h3>
+<h3>2.21.2 Defects Fixed</h3>
 <ul>
 <li>getCriticalExtensionOIDs on an X.509 attribute certificate was returning the non-critical set. This has been fixed.
 <li>Encoding uncompressed ECDSA keys could occasionally introduce an extra leading zero byte. This has been fixed.
@@ -649,7 +659,7 @@ Release 1.31
 This has been fixed.
 <li>OIDs with extremely large components would sometimes reencode with unnecessary bytes in their encoding. The optimal DER encoding will now be produced instead.
 </ul>
-<h3>2.20.3 Additional Features and Functionality</h3>
+<h3>2.21.3 Additional Features and Functionality</h3>
 <ul>
 <li>The SMIME package now supports the large file streaming model as well.
 <li>Additional ASN.1 message support has been added for RFC 3739 in the org.bouncycastle.x509.qualified package.
@@ -658,9 +668,9 @@ This has been fixed.
 <li>CertPathValidator has been updated to better support path validation as defined in RFC 3280.
 </ul>
 
-<h3>2.21.1 Version</h3>
+<h3>2.22.1 Version</h3>
 Release 1.30
-<h3>2.21.2 Defects Fixed</h3>
+<h3>2.22.2 Defects Fixed</h3>
 <ul>
 <li>Whirlpool was calculating the wrong digest for 31 byte data and could throw an exception for some other data lengths. This has been fixed.
 <li>AlgorithmParameters for IVs were returning a default of RAW encoding of the parameters when they should have been returning an
@@ -672,7 +682,7 @@ ASN.1 encoding. This has been fixed.
 <li>KEKIdentifier would not handle OtherKeyAttribute objects correctly. This has been fixed.
 <li>GetCertificateChain on a PKCS12 keystore would return a single certificate chain rather than null if the alias passed in represented a certificate not a key. This has been fixed.
 </ul>
-<h3>2.21.3 Additional Features and Functionality</h3>
+<h3>2.22.3 Additional Features and Functionality</h3>
 <ul>
 <li>RSAEngine no longer assumes keys are byte aligned when checking for out of range input.
 <li>PGPSecretKeyRing.removeSecretKey and PGPSecretKeyRing.insertSecretKey have been added.
@@ -683,9 +693,9 @@ ASN.1 encoding. This has been fixed.
 <li>Both the lightweight API and the provider now support the Camellia encryption algorithm.
 </ul>
 
-<h3>2.22.1 Version</h3>
+<h3>2.23.1 Version</h3>
 Release 1.29
-<h3>2.22.2 Defects Fixed</h3>
+<h3>2.23.2 Defects Fixed</h3>
 <ul>
 <li>HMac-SHA384 and HMac-SHA512 were not IETF compliant. This has been fixed.
 <li>The equals() method on ElGamalKeyParameters and DHKeyParameters in the lightweight API would sometimes
@@ -696,7 +706,7 @@ version 3 key valid days field.
 <li>ISO9796 signatures for full recovered messsages could incorrectly verify for similar messages in some circumstances. This has been fixed.
 <li>The occasional problem with decrypting PGP messages containing compressed streams now appears to be fixed.
 </ul>
-<h3>2.22.3 Additional Features and Functionality</h3>
+<h3>2.23.3 Additional Features and Functionality</h3>
 <ul>
 <li>Support has been added for the OIDs and key generation required for HMac-SHA224, HMac-SHA256, HMac-SHA384, and 
 HMac-SHA512.
@@ -704,14 +714,14 @@ HMac-SHA512.
 <li>The provider and the lightweight API now support the GOST-28147-94 MAC algorithm.
 <li>Headers are now settable for PGP armored output streams.
 </ul>
-<h3>2.22.4 Notes</h3>
+<h3>2.23.4 Notes</h3>
 <ul>
 <li>The old versions of HMac-SHA384 and HMac-SHA512 can be invoked as OldHMacSHA384 and OldHMacSHA512, or by using the OldHMac class in the
 lightweight API.
 </ul> 
-<h3>2.23.1 Version</h3>
+<h3>2.24.1 Version</h3>
 Release 1.28
-<h3>2.23.2 Defects Fixed</h3>
+<h3>2.24.2 Defects Fixed</h3>
 <ul>
 <li>Signatures on binary encoded S/MIME messages could fail to validate when correct. This has been fixed.
 <li>getExtensionValue() on CRL Entries were returning the encoding of the inner object, rather than the octet string. This has been fixed.
@@ -725,7 +735,7 @@ Release 1.28
 <li>Filetype for S/MIME compressed messages was incorrect. This has been fixed.
 <li>BigInteger class can now create negative numbers from byte arrays.
 </ul>
-<h3>2.23.3 Additional Features and Functionality</h3>
+<h3>2.24.3 Additional Features and Functionality</h3>
 <ul>
 <li>S/MIME now does canonicalization on non-binary input for signatures.
 <li>Micalgs for the new SHA schemes are now supported.
@@ -736,16 +746,16 @@ Release 1.28
 <li>Support has been added for the creation of ECDSA certificate requests.
 <li>The provider and the light weight API now support the WHIRLPOOL message digest.
 </ul>
-<h3>2.23.4 Notes</h3>
+<h3>2.24.4 Notes</h3>
 <ul>
 <li>Patches for S/MIME binary signatures and canonicalization were actually applied in 1.27, but a couple of days after the release - if the class 
 CMSProcessableBodyPartOutbound is present in the package org.bouncycastle.mail.smime you have the patched 1.27. We would recommend upgrading to 1.28 in any case
 as some S/MIME 3.1 recommendations have also been introduced for header creation.
 <li>GOST private keys are probably not encoding correctly and can be expected to change.
 </ul>
-<h3>2.24.1 Version</h3>
+<h3>2.25.1 Version</h3>
 Release 1.27
-<h3>2.24.2 Defects Fixed</h3>
+<h3>2.25.2 Defects Fixed</h3>
 <ul>
 <li>Typos in the provider which pointed Signature algorithms SHA256WithRSA, SHA256WithRSAEncryption, SHA384WithRSA, SHA384WithRSAEncryption, SHA512WithRSA, and SHA512WithRSAEncryption at the PSS versions of the algorithms have been fixed. The correct names for the PSS algorithms are SHA256withRSAandMGF1, SHA384withRSAandMGF1, and SHA512withRSAandMGF1.
 <li>X509CertificateFactory failed under some circumstances to reset properly if the input stream being passed
@@ -759,7 +769,7 @@ to generateCertificate(s)() changed, This has been fixed.
 <li>TSP TimeStampToken was failing to validate time stamp tokens with the issuerSerial field set in the ESSCertID structure. This has been fixed.
 <li>Path validation in environments with frequently updated CRLs could occasionally reject a valid path. This has been fixed.
 </ul>
-<h3>2.24.3 Additional Features and Functionality</h3>
+<h3>2.25.3 Additional Features and Functionality</h3>
 <ul>
 <li>Full support has been added for the OAEPParameterSpec class to the JDK 1.5 povider.
 <li>Full support has been added for the PSSParameterSpec class to the JDK 1.4 and JDK 1.5 providers.
@@ -770,7 +780,7 @@ prevent applications being vunerable to oracle attacks.
 <li>The CertPath support classes now support PKCS #7 encoding.
 <li>Point compression can now be turned off when encoding elliptic curve keys.
 </ul>
-<h3>2.24.4 Changes that may affect compatibility</h3>
+<h3>2.25.4 Changes that may affect compatibility</h3>
 <ul>
 <li>org.bouncycastle.jce.interfaces.ElGamalKey.getParams() has been changed to getParameters() to avoid clashes with
 a JCE interface with the same method signature.
@@ -779,9 +789,9 @@ with a JCE interface with the same method signature. The getParams() method in p
 <li>SHA256WithRSAEncryption, SHA384WithRSAEncryption, SHA512WithRSAEncryption now refer to their PKCS #1 V1.5 implementations. If you
 were using these previously you should use SHA256WithRSAAndMGF1, SHA384WithRSAAndMGF1, or SHA512WithRSAAndMGF1.
 </ul>
-<h3>2.25.1 Version</h3>
+<h3>2.26.1 Version</h3>
 Release 1.26
-<h3>2.25.2 Defects Fixed</h3>
+<h3>2.26.2 Defects Fixed</h3>
 <ul>
 <li>The X.509 class UserNotice assumed some of the optional fields were not optional. This has been fixed.
 <li>BCPGInputStream would break on input packets of 8274 bytes in length. This has been fixed.
@@ -790,7 +800,7 @@ Release 1.26
 <li>ASN1Sets now properly sort their contents when created from scratch.
 <li>A bug introduced in the CertPath validation in the last release which meant some certificate paths would validate if they were invalid has been fixed.
 </ul>
-<h3>2.25.3 Additional Features and Functionality</h3>
+<h3>2.26.3 Additional Features and Functionality</h3>
 <ul>
 <li>Support for JDK 1.5 naming conventions for OAEP encryption and PSS signing has been added.
 <li>Support for Time Stamp Protocol (RFC 3161) has been added.
@@ -800,14 +810,14 @@ Release 1.26
 <li>PBEWithMD5AndRC2, PBEWithSHA1AndRC2 now generate keys rather than exceptions.
 <li>The BigInteger implementation has been further optimised to take more advantage of the Montgomery number capabilities.
 </ul>
-<h3>2.25.4 JDK 1.5 Changes</h3>
+<h3>2.26.4 JDK 1.5 Changes</h3>
 <ul>
 <li>The JDK 1.5 version of the provider now supports the new Elliptic Curve classes found in the java.security packages. Note: while we have tried to preserve some backwards compatibility people using Elliptic curve are likely to find some minor code changes are required when moving code from JDK 1.4 to JDK 1.5 as the java.security APIs have changed.
 </ul>
 
-<h3>2.26.1 Version</h3>
+<h3>2.27.1 Version</h3>
 Release 1.25
-<h3>2.26.2 Defects Fixed</h3>
+<h3>2.27.2 Defects Fixed</h3>
 <ul>
 <li>In some situations OpenPGP would overread when a stream had been
 broken up into partial blocks. This has been fixed.
@@ -829,7 +839,7 @@ stores them as BMP strings.
 <li>Parsing a message with a zero length body with SMIMESigned would cause an exception. This has been fixed.
 <li>Some versions of PGP use zeros in the data stream rather than a replication of the last two bytes of the iv as specified in the RFC to determine if the correct decryption key has been found. The decryption classes will now cope with both.
 </ul>
-<h3>2.26.3 Additional Features and Functionality</h3>
+<h3>2.27.3 Additional Features and Functionality</h3>
 <ul>
 <li>Support for extracting signatures based on PGP user attributes has been
 added to PGPPublicKey.
@@ -848,9 +858,9 @@ having to convert the original object down to its base ASN.1 equivalents.
 <li>Trailing bit complement (TBC) padding has been added.
 <li>OID components of up to 2^63 bits are now supported.
 </ul>
-<h3>2.27.1 Version</h3>
+<h3>2.28.1 Version</h3>
 Release 1.24
-<h3>2.27.2 Defects Fixed</h3>
+<h3>2.28.2 Defects Fixed</h3>
 <ul>
 <li>OpenPGP Secret key rings now parse key rings with user attribute packets in them correctly.
 <li>OpenPGP Secret key rings now parse key rings with GPG comment packets in them.
@@ -867,15 +877,15 @@ being explicitly provided and data length was a multiple of the block size. This
 <li>An encoding error introduced in 1.23 which affected generation of the
 KeyUsage extension has been fixed.
 </ul>
-<h3>2.27.3 Additional Features and Functionality</h3>
+<h3>2.28.3 Additional Features and Functionality</h3>
 <ul>
 <li>PKCS12 keystore now handles single key/certificate files without any attributes present.
 <li>Support for creation of PGPKeyRings incorporating sub keys has been added.
 <li>ZeroPadding for encrypting ASCII data has been added.
 </ul>
-<h3>2.28.1 Version</h3>
+<h3>2.29.1 Version</h3>
 Release 1.23
-<h3>2.28.2 Defects Fixed</h3>
+<h3>2.29.2 Defects Fixed</h3>
 <ul>
 <li>Reading a PGP Secret key file would sometimes cause a class cast exception. This has been fixed.
 <li>PGP will now read SecretKeys which are encrypted with the null algorithm.
@@ -890,7 +900,7 @@ it to occasionally generate the wrong key has been fixed.
 <li>X509Name class will now print names with nested pairs in component sets correctly.
 <li>RC4 now resets correctly on doFinal.
 </ul>
-<h3>2.28.3 Additional Features and Functionality</h3>
+<h3>2.29.3 Additional Features and Functionality</h3>
 <ul>
 <li>PGP V3 keys and V3 signature generation is now supported.
 <li>Collection classes have been added for representing files of PGP public and secret keys.
@@ -909,9 +919,9 @@ certifications has been added.
 <li>DERGeneralizedTime getTime() method now handles a broader range of input strings.
 </ul>
 
-<h3>2.29.1 Version</h3>
+<h3>2.30.1 Version</h3>
 Release 1.22
-<h3>2.29.2 Defects Fixed</h3>
+<h3>2.30.2 Defects Fixed</h3>
 <ul>
 <li>Generating DSA signatures with PGP would cause a class cast exception, this has been fixed.
 <li>PGP Data in the 192 to 8383 byte length would sometimes be written with the wrong length header. This has been fixed.
@@ -921,7 +931,7 @@ a non-null reason, rather than a null one. This has been fixed.
 <li>PSS signature verification would fail approximately 0.5 % of the time on correct signatures. This has been fixed.
 <li>Encoding of CRL Distribution Points now always works.
 </ul>
-<h3>2.29.3 Additional Features and Functionality</h3>
+<h3>2.30.3 Additional Features and Functionality</h3>
 <ul>
 <li>Additional methods for getting public key information have been added to the PGP package.
 <li>Some support for user attributes and the image attribute tag has been added.
@@ -929,9 +939,9 @@ a non-null reason, rather than a null one. This has been fixed.
 <li>Support for ElGamal encryption/decryption has been added to the PGP package.
 </ul>
 
-<h3>2.30.1 Version</h3>
+<h3>2.31.1 Version</h3>
 Release 1.21
-<h3>2.30.2 Defects Fixed</h3>
+<h3>2.31.2 Defects Fixed</h3>
 <ul>
 <li>The CertPath validator would fail for some valid CRLs. This has been  fixed.
 <li>AES OIDS for S/MIME were still incorrect, this has been fixed.
@@ -939,16 +949,16 @@ Release 1.21
 <li>The J2ME BigInteger class would sometimes go into an infinite loop generating prime numbers. This has been fixed.
 <li>DERBMPString.equals() would throw a class cast exception. This has been fixed.
 </ul>
-<h3>2.30.3 Additional Features and Functionality</h3>
+<h3>2.31.3 Additional Features and Functionality</h3>
 <ul>
 <li>PEMReader now handles public keys.
 <li>OpenPGP/BCPG should now handle partial input streams. Additional methods for reading subpackets off signatures.
 <li>The ASN.1 library now supports policy qualifiers and policy info objects.
 </ul>
 
-<h3>2.31.1 Version</h3>
+<h3>2.32.1 Version</h3>
 Release 1.20
-<h3>2.31.2 Defects Fixed</h3>
+<h3>2.32.2 Defects Fixed</h3>
 <ul>
 <li>BigInteger toString() in J2ME/JDK1.0 now produces same output as the Sun one.
 <li>RSA would throw a NullPointer exception with doFinal without arguments. This has been fixed.
@@ -958,7 +968,7 @@ Release 1.20
 <li>AES OIDS were incorrect, this has been fixed.
 <li>In some cases BC generated private keys would not work with the JSSE. This has been fixed.
 </ul>
-<h3>2.31.3 Additional Features and Functionality</h3>
+<h3>2.32.3 Additional Features and Functionality</h3>
 <ul>
 <li>Support for reading/writing OpenPGP public/private keys and OpenPGP signatures has been added.
 <li>Support for generating OpenPGP PBE messages and public key encrypted messages has been added.
@@ -966,9 +976,9 @@ Release 1.20
 <li>Addition of a Null block cipher to the light weight API.
 </ul>
 
-<h3>2.32.1 Version</h3>
+<h3>2.33.1 Version</h3>
 Release 1.19
-<h3>2.32.2 Defects Fixed</h3>
+<h3>2.33.2 Defects Fixed</h3>
 <ul>
 <li>The PKCS12 store would throw an exception reading PFX files that had attributes with no values. This has been fixed.
 <li>RSA Private Keys would not serialise if they had PKCS12 bag attributes attached to them, this has been fixed.
@@ -976,7 +986,7 @@ Release 1.19
 <li>ASN1 parser would sometimes mistake an implicit null for an implicit empty
 sequence. This has been fixed.
 </ul>
-<h3>2.32.3 Additional Features and Functionality</h3>
+<h3>2.33.3 Additional Features and Functionality</h3>
 <ul>
 <li>S/MIME and CMS now support the draft standard for AES encryption.
 <li>S/MIME and CMS now support setable key sizes for the standard algorithms.
@@ -988,9 +998,9 @@ and the processing of responses. Response generation is also provided, but shoul
 in order to find algorithms.
 </ul>
 
-<h3>2.33.1 Version</h3>
+<h3>2.34.1 Version</h3>
 Release 1.18
-<h3>2.33.2 Defects Fixed</h3>
+<h3>2.34.2 Defects Fixed</h3>
 <ul>
 <li>DESKeySpec.isParityAdjusted in the clean room JCE could go into an
 infinite loop. This has been fixed.
@@ -1001,7 +1011,7 @@ input stream. This has been fixed.
 <li>Seeding with longs in the SecureRandom for the J2ME and JDK 1.0,
 only used 4 bytes of the seed value. This has been fixed.
 </ul>
-<h3>2.33.3 Additional Features and Functionality</h3>
+<h3>2.34.3 Additional Features and Functionality</h3>
 <ul>
 <li>The X.509 OID for RSA is now recognised by the provider as is the OID for RSA/OAEP.
 <li>Default iv's for DES are now handled correctly in CMS.
@@ -1012,9 +1022,9 @@ of "application/pkcs7-mime; smime-type=signed-data;" signatures.
 <li>Diffie-Hellman key generation is now faster in environments using the
 Sun BigInteger library.
 </ul>
-<h3>2.34.1 Version</h3>
+<h3>2.35.1 Version</h3>
 Release 1.17
-<h3>2.34.2 Defects Fixed</h3>
+<h3>2.35.2 Defects Fixed</h3>
 <ul>
 <li>Reuse of an CMSSignedObject could occasionally result in a class
 cast exception. This has been fixed.
@@ -1025,7 +1035,7 @@ with only the required parameter. This has been fixed.
 <li>The DERObject constructor in OriginatorIdentifierOrKey was leaving 
 the id field as null. This has been fixed.
 </ul>
-<h3>2.34.2 Additional Functionality and Features</h3>
+<h3>2.35.2 Additional Functionality and Features</h3>
 <ul>
 <li>RC2 now supports the full range of parameter versions and effective
 key sizes.
@@ -1045,9 +1055,9 @@ be set when a string is converted as well as changeable lookup tables for
 string to OID conversion.
 </ul>
 
-<h3>2.35.1 Version</h3>
+<h3>2.36.1 Version</h3>
 Release 1.16
-<h3>2.35.2 Defects Fixed</h3>
+<h3>2.36.2 Defects Fixed</h3>
 <ul>
 <li>CRLS were only working for UTC time constructed Time objects, this has
 been fixed.
@@ -1061,7 +1071,7 @@ compatibility with older CMS/SMIME clients have been fixed.
 to throw a NullPointerException at the wrong time.
 <li>Macs now clone correctly in the clean room JCE.
 </ul>
-<h3>2.35.3 Additional Functionality and Features</h3>
+<h3>2.36.3 Additional Functionality and Features</h3>
 <ul>
 <li>PGPCFB support has been added to the provider and the lightweight API.
 <li>There are now three versions of the AESEngine, all faster than before,
@@ -1078,9 +1088,9 @@ size of the package for use with the lightweight API.
 of the Cert Path API, remove code suited to inclusion in the provider,
 and to support multiple recipients/signers.
 </ul>
-<h3>2.36.1 Version</h3>
+<h3>2.37.1 Version</h3>
 Release 1.15
-<h3>2.36.2 Defects Fixed</h3>
+<h3>2.37.2 Defects Fixed</h3>
 <ul>
 <li>The base string for the oids in asn1.x509.KeyPurposeId was incorrect. This
 has been fixed.
@@ -1103,7 +1113,7 @@ precedence over the local alias used to add the key to the PKCS12 key store.
 The local name now takes precedence.
 <li>ReasonFlags now correctly encodes.
 </ul>
-<h3>2.36.3 Additional Functionality and Features</h3>
+<h3>2.37.3 Additional Functionality and Features</h3>
 <ul>
 <li>The PKCS12 key store now handles key bags in encryptedData bags.
 <li>The X509NameTokenizer now handles for '\' and '"' characters.
@@ -1111,9 +1121,9 @@ The local name now takes precedence.
 <li>The ASN.1 library now supports ENUMERATED, UniversalString and the X.509 library support for CRLs now includes CRLReason, and some elements of CertificatePolicies.
 <li>Both the provider and the lightweight library now support a basic SIC mode for block ciphers.
 </ul>
-<h3>2.37.1 Version</h3>
+<h3>2.38.1 Version</h3>
 Release 1.14
-<h3>2.37.2 Defects Fixed</h3>
+<h3>2.38.2 Defects Fixed</h3>
 <ul>
 <li>there was a bug in the BigInteger right shifting for > 31 bit shifts.
 This has been fixed.
@@ -1134,7 +1144,7 @@ order for each of the 3 words making up the digest. This has been fixed.
 <li>asn1.x509.ExtendedKeyUsage used to through a null pointer exception
 on construction. This has been fixed.
 </ul>
-<h3>2.37.3 Additional Functionality and Features</h3>
+<h3>2.38.3 Additional Functionality and Features</h3>
 <ul>
 <li>The BigInteger library now uses Montgomery numbers for modPow and is
 substantially faster.
@@ -1147,9 +1157,9 @@ These deal with implicit/explicit tagging ambiguities with constructed types.
 <li>The X.509 certificate factory supports a wider range of encodings and
 object identifiers.
 </ul>
-<h3>2.38.1 Version</h3>
+<h3>2.39.1 Version</h3>
 Release 1.13
-<h3>2.38.2 Defects Fixed</h3>
+<h3>2.39.2 Defects Fixed</h3>
 <ul>
     <li>The TBSCertificate object in the ASN.1 library now properly implements
     the Time object, rather returning UTC time.
@@ -1159,7 +1169,7 @@ Release 1.13
     results for negative numbers. This has been Fixed.
 </ul>
 
-<h3>2.38.3 Additional Functionality and Features</h3>
+<h3>2.39.3 Additional Functionality and Features</h3>
 <ul>
     <li>The key to keySpec handling of the secret key factories has been improved.
     <li>There is now a SMIME implementation and a more complete CMS
@@ -1174,9 +1184,9 @@ Release 1.13
     length certificate chains for signing keys.
 </ul>
 
-<h3>2.39.1 Version</h3>
+<h3>2.40.1 Version</h3>
 Release 1.12
-<h3>2.39.2 Defects Fixed</h3>
+<h3>2.40.2 Defects Fixed</h3>
 <ul>
     <li>The ASN.1 library was unable to read an empty set object. This has been fixed.
     <li>Returning sets of critical and non-critical extensions on X.509 certificates could result in a null pointer exception if the certificate had no extensions. This has been fixed.
@@ -1195,7 +1205,7 @@ Release 1.12
     <li>the IV algorithm parameters class would improperly throw an exception
     on initialisation. This has been fixed.
 </ul>
-<h3>2.39.3 Additional Functionality and Features</h3>
+<h3>2.40.3 Additional Functionality and Features</h3>
 <ul>
     <li>The AESWrap ciphers will now take IV's.
     <li>The DES-EDEWrap algorithm described in http://www.ietf.org/internet-drafts/draft-ietf-smime-key-wrap-01.txt is now supported.
@@ -1208,9 +1218,9 @@ Release 1.12
     <li>Base support for CMS (RFC 2630) is now provided (see CONTRIBUTORS file
     for details).
 </ul>
-<h3>2.40.1 Version</h3>
+<h3>2.41.1 Version</h3>
 Release 1.11
-<h3>2.40.2 Defects Fixed</h3>
+<h3>2.41.2 Defects Fixed</h3>
 <ul>
 <li>X9.23 padding of MACs now works correctly with block size aligned data.
 <li>Loading a corrupted "UBER" key store would occasionally cause the
@@ -1236,7 +1246,7 @@ been fixed.
 extensions. This has been fixed.
 <li>The NetscapeCert type bits were reversed! This has been fixed.
 </ul>
-<h3>2.40.3 Additional Functionality and Features</h3>
+<h3>2.41.3 Additional Functionality and Features</h3>
 <ul>
 <li>The lightweight API and the JCE provider now support ElGamal.
 <li>X509Principal, and X509Name now supports the "DC" attribute and the
@@ -1250,16 +1260,16 @@ the Sun keytool - it always uses the default provider for creating certificates.
 <li>Elliptic curve routines now handle uncompressed points as well as the
 compressed ones.
 </ul>
-<h3>2.40.4 Other changes</h3>
+<h3>2.41.4 Other changes</h3>
 <ul>
 <li>As the range of public key types supported has expanded the getPublicKey
 method on the SubjectPublicKeyInfo class is not always going to work. The
 more generic method getPublicKeyData has been added and getPublicKey now
 throws an IOException if there is a problem.
 </ul>
-<h3>2.41.1 Version</h3>
+<h3>2.42.1 Version</h3>
 Release 1.10
-<h3>2.41.2 Defects Fixed</h3>
+<h3>2.42.2 Defects Fixed</h3>
 <ul>
 <li>The PKCS12 Key Store now interoperates with the JDK key tool. <b>Note:</b> this does mean the the key name passed to the setKeyEntry calls has become
 significant.
@@ -1267,7 +1277,7 @@ significant.
 has been fixed.
 <li>The ASN.1 input streams now handle zero-tagged zero length objects correctly.
 </ul>
-<h3>2.41.3 Additional Functionality and Features</h3>
+<h3>2.42.3 Additional Functionality and Features</h3>
 <ul>
 <li>The JCE Provider and the lightweight API now support Serpent, CAST5, and CAST6.
 <li>The JCE provider and the lightweight API now has an implementation of ECIES.
@@ -1276,9 +1286,9 @@ be kept long term as it may be adjusted.
 <li>Further work has been done on performance - mainly in the symmetric ciphers.
 <li>Support for the generation of PKCS10 certification requests has been added.
 </ul>
-<h3>2.42.1 Version</h3>
+<h3>2.43.1 Version</h3>
 Release 1.09
-<h3>2.42.2 Defects Fixed</h3>
+<h3>2.43.2 Defects Fixed</h3>
 <ul>
 <li>failure to pass in an RC5 parameters object now results in an exception
 at the upper level of the JCE, rather than falling over in the lightweight
@@ -1291,7 +1301,7 @@ This has been fixed.
 <li>In some cases the ASN.1 library wouldn't handle implicit tagging properly.
 This has been fixed.
 </ul>
-<h3>2.42.3 Additional Functionality and Features</h3>
+<h3>2.43.3 Additional Functionality and Features</h3>
 <ul>
 <li>Support for RC5-64 has been added to the JCE.
 <li>ISO9796-2 signatures have been added to the JCE and lightweight API.
@@ -1315,10 +1325,10 @@ currently consists of a class showing how to generate a PKCS12 file.
 resource hungry and faster - whether it's fast enough remains to be seen!
 </ul>
 
-<h3>2.43.1 Version</h3>
+<h3>2.44.1 Version</h3>
 Release 1.08
 
-<h3>2.43.2 Defects Fixed</h3>
+<h3>2.44.2 Defects Fixed</h3>
 <ul>
 <li>It wasn't possible to specify an ordering for distinguished names in
 X509 certificates. This is now supported.
@@ -1329,7 +1339,7 @@ if it could be processed. This has been fixed.
 <li>The netscape certificate request class wouldn't compile under JDK 1.1. This
 has been fixed.
 </ul>
-<h3>2.43.3 Additional Functionality and Features</h3>
+<h3>2.44.3 Additional Functionality and Features</h3>
 <ul>
 <li>ISO 9796-1 padding is now supported with RSA in the lightweight
 API and the JCE.
@@ -1342,10 +1352,10 @@ compatibility purposes only - we recommend you don't use them for anything new!
 the collections class was not present. Thanks to a donated collections API
 this is fixed.
 </ul>
-<h3>2.44.1 Version</h3>
+<h3>2.45.1 Version</h3>
 Release 1.07
 
-<h3>2.44.2 Defects Fixed</h3>
+<h3>2.45.2 Defects Fixed</h3>
 <ul>
 <li>It turned out that the setOddParity method in the DESParameter class
 was indeed doing something odd but not what was intended. This is now
@@ -1355,10 +1365,10 @@ accessed by prepending the work "Broken" in front of the original PBE cipher
 call. If you want an example of how to deal with this as a migration issue
 have a look in org.bouncycastle.jce.provider.JDKKeyStore lines 201-291.
 </ul>
-<h3>2.45.1 Version</h3>
+<h3>2.46.1 Version</h3>
 Release 1.06
 
-<h3>2.45.2 Defects Fixed</h3>
+<h3>2.46.2 Defects Fixed</h3>
 <ul>
 <li>Diffie-Hellman keys are now properly serialisable as well as
 encodable.
@@ -1381,17 +1391,17 @@ result in a null pointer exception. This has been fixed.
 caused a NullPointer exception. This has been fixed.
 </ul>
 
-<h3>2.45.3 Additional Functionality</h3>
+<h3>2.46.3 Additional Functionality</h3>
 <ul>
 <li>ISO10126Padding is now recognised explicitly for block ciphers
 as well.
 <li>The Blowfish implementation is now somewhat faster.
 </ul>
 
-<h3>2.46.1 Version</h3>
+<h3>2.47.1 Version</h3>
 Release 1.05
 
-<h3>2.46.2 Defects Fixed</h3>
+<h3>2.47.2 Defects Fixed</h3>
 <ul>
 <li>The DESEDE key generator can now be used to generate 2-Key-DESEDE
 keys as well as 3-Key-DESEDE keys.
@@ -1402,22 +1412,22 @@ key correctly (depending on the digest used). This has been fixed.
 <li>The ASN.1 library was skipping explicitly tagged objects of zero length.
 This has been fixed.
 </ul>
-<h3>2.46.3 Additional Functionality</h3>
+<h3>2.47.3 Additional Functionality</h3>
 <ul>
 <li>There is now an org.bouncycastle.jce.netscape package which has
 a class in for dealing with Netscape Certificate Request objects.
 </ul>
-<h3>2.46.4 Additional Notes</h3>
+<h3>2.47.4 Additional Notes</h3>
 <p>
 Concerning the PKCS12 fix: in a few cases this may cause some backward
 compatibility issues - if this happens to you, drop us a line at
 <a href="mailto:feedback-crypto@bouncycastle.org">feedback-crypto@bouncycastle.org</a>
 and we will help you get it sorted out.
 
-<h3>2.47.1 Version</h3>
+<h3>2.48.1 Version</h3>
 Release 1.04
 
-<h3>2.47.2 Defects Fixed</h3>
+<h3>2.48.2 Defects Fixed</h3>
 <ul>
 <li>Signatures generated by other providers that include optional null
 parameters in the AlgorithmIdentifier are now handled correctly by the
@@ -1446,7 +1456,7 @@ been fixed.
 hash table when the hash table constructor was called. This has been fixed.
 </ul>
 
-<h3>2.47.3 Additional Functionality</h3>
+<h3>2.48.3 Additional Functionality</h3>
 <ul>
 <li>Added Elliptic Curve DSA (X9.62) - ECDSA - to provider and lightweight
 library.
@@ -1458,10 +1468,10 @@ to lightweight library.
 <li>The certificate generators now support ECDSA and DSA certs as well.
 </ul>
 
-<h3>2.48.1 Version</h3>
+<h3>2.49.1 Version</h3>
 Release 1.03
 
-<h3>2.48.2 Defects Fixed</h3>
+<h3>2.49.2 Defects Fixed</h3>
 <ul>
 <li>CFB and OFB modes when specified without padding would insist on input
 being block aligned. When specified without padding CFB and OFB now behave in a compatible 
@@ -1471,29 +1481,29 @@ In short, it provides another way of generating cipher text the same
 length as the plain text.
 </ul>
 
-<h3>2.49.1 Version</h3>
+<h3>2.50.1 Version</h3>
 Release 1.02
 
-<h3>2.49.2 Defects Fixed</h3>
+<h3>2.50.2 Defects Fixed</h3>
 <ul>
 <li>The RSA key pair generator occasionally produced keys 1 bit under the
 requested size. This is now fixed.
 </ul>
 
-<h3>2.50.1 Version</h3>
+<h3>2.51.1 Version</h3>
 Release 1.01
 
-<h3>2.50.2 Defects Fixed</h3>
+<h3>2.51.2 Defects Fixed</h3>
 
 <ul>
 <li>Buffered ciphers in lightweight library were not resetting correctly
 on a doFinal. This has been fixed.
 </ul>
 
-<h3>2.51.1 Version</h3>
+<h3>2.52.1 Version</h3>
 Release 1.0 
 
-<h3>2.51.2 Defects Fixed</h3>
+<h3>2.52.2 Defects Fixed</h3>
 <p>
 <ul>
 <li>JDK1.2 version now works with keytool for certificate generation.
@@ -1508,7 +1518,7 @@ by the RSA key factory. This is now fixed.
 <li>Some DES PBE algorithms did not set the parity correctly in generated keys, this has been fixed.
 </ul>
 
-<h3>2.51.3 Additional functionality</h3>
+<h3>2.52.3 Additional functionality</h3>
 <p>
 <ul>
 <li>Argument validation is much improved.