</ul><h3>2.26.1 Version</h3>Release 1.09<h3>2.26.2 Defects Fixed</h3><ul><li>failure to pass in an RC5 parameters object now results in an exceptionat the upper level of the JCE, rather than falling over in the lightweightlibrary.<li>ISO10126Padding now incorporates the correct amount of random data.<li>The PKCS12 key store wasn't picking up certificate chains properlywhen being used to write PKCS12 files. This has been fixed.<li>The Twofish engine would call System.exit if the key was too large.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.26.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.<li>A more general paddings packge for use with MACs and block ciphers had been aded to the lightweight API. MACs now allow you to specify padding.<li>X9.23 Padding has been added to the JCE and lightwieght API. The oldPaddedBlockCipher class is now deprecated see org.bouncycastle.crypto.paddings for details.<li>SHA-256, SHA-384, and SHA-512 are now added. Note: while the public reviewperiod has finished, these algorithms have not yet been standardised, in theevent that final standardisation changes the algorithms these implementationswill be changed.<li>It's now possible to set bag attributes on items to go into a PKCS12 store,using the org.bouncycastle.jce.interfaces.PKCS12BagAttributeCarrier interface.<li>More classses have been added to the ASN.1 package for dealing withcertificate extensions and CRLs including a CRL generator. Note: theCRL generators should be regarded as under development and subject to change.<li>There's now an examples package for the JCE (in addition to the examplesin org.bouncycastle.jce.provider.test) - org.bouncycastle.jce.examples. Itcurrently consists of a class showing how to generate a PKCS12 file.<li>The X.509 CertificateFactory now includes CRL support.  DER or PEM CRLs may be processed.<li>The BigInteger library has been written with a view to making it lessresource hungry and faster - whether it's fast enough remains to be seen!</ul><h3>2.27.1 Version</h3>Release 1.08<h3>2.27.2 Defects Fixed</h3><ul><li>It wasn't possible to specify an ordering for distinguished names inX509 certificates. This is now supported.<li>In some circumstances stream Ciphers in the JCE would cause null pointerexceptions on doFinal. This has been fixed.<li>Unpadded ciphers would sometimes buffer the last block of input, evenif it could be processed. This has been fixed.<li>The netscape certificate request class wouldn't compile under JDK 1.1. Thishas been fixed.</ul><h3>2.27.3 Additional Functionality and Features</h3><ul><li>ISO 9796-1 padding is now supported with RSA in the lightweightAPI and the JCE.<li>support classes have been added for reading and writing PKCS 12 files,including a keystore for the JCA.<li>The message digests MD4, Tiger, and RIPEMD128 have been added to theJCE and the lightweight API. Note: MD4 and RIPEMD128 have been added forcompatibility purposes only - we recommend you don't use them for anything new!<li>The JDK 1.1 certificate classes didn't conform to the JDK 1.2 API asthe collections class was not present. Thanks to a donated collections APIthis is fixed.</ul><h3>2.28.1 Version</h3>Release 1.07<h3>2.28.2 Defects Fixed</h3><ul><li>It turned out that the setOddParity method in the DESParameter classwas indeed doing something odd but not what was intended. This is nowfixed. <b>Note:</b>This will affect some PBE encryptions that were carriedout with DES, equivalent PBE ciphers to the old PBE DES cipher can beaccessed by prepending the work "Broken" in front of the original PBE ciphercall. If you want an example of how to deal with this as a migration issuehave a look in org.bouncycastle.jce.provider.JDKKeyStore lines 201-291.</ul><h3>2.29.1 Version</h3>Release 1.06<h3>2.29.2 Defects Fixed</h3><ul><li>Diffie-Hellman keys are now properly serialisable as well asencodable.<li>Three of the semi-weak keys in the DESParameters, and the DESKeySpec lookup table, were incorrect. This has been fixed.<li>DESEDE key generators now accept 112 and 168 as the key sizes, as wellas 128 and 192 (for those people who don't like to count the parity bits).<li>Providing no strength parameter is passed to the DESede key generator inthe JCE provider, the provider now generates DESede keys in the k1-k2-k1format (which is compatible with the Sun reference implementation), otherwiseyou get what you ask for (3-DES or 2-DES in the minimum number of bytes).<li>Base Diffie-Hellman key agreement now works correctly for more than twoparties.<li>Cipher.getAlgorithmParameters was returing null in cases where a cipherobject had generated it's own IV. This has been fixed.<li>An error in the key store occasionally caused checks of entry types toresult in a null pointer exception. This has been fixed.<li>RSA key generator in JCE now recognises RSAKeyGenerationParameterSpec.<li>Resetting and resusing HMacs in the lightweight and heavyweight librariescaused a NullPointer exception. This has been fixed.</ul><h3>2.29.3 Additional Functionality</h3><ul><li>ISO10126Padding is now recognised explicitly for block ciphersas well.<li>The Blowfish implementation is now somewhat faster.</ul><h3>2.30.1 Version</h3>Release 1.05<h3>2.30.2 Defects Fixed</h3><ul><li>The DESEDE key generator can now be used to generate 2-Key-DESEDEkeys as well as 3-Key-DESEDE keys.<li>One of the weak keys in the DESParameters, and the DESKeySpec lookup table, was incorrect. This has been fixed.<li>The PKCS12 generator was only generating the first 128-160 bits of thekey 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.30.3 Additional Functionality</h3><ul><li>There is now an org.bouncycastle.jce.netscape package which hasa class in for dealing with Netscape Certificate Request objects.</ul><h3>2.30.4 Additional Notes</h3><p>Concerning the PKCS12 fix: in a few cases this may cause some backwardcompatability 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.31.1 Version</h3>Release 1.04<h3>2.31.2 Defects Fixed</h3><ul><li>Signatures generated by other providers that include optional nullparameters in the AlgorithmIdentifier are now handled correctly by theprovider.<li>The JCE 1.2.1 states that the names of algorithms associated with the JCEare case insensitive. The class that matches algorithms to names now triesto match the name given with it's equivalent in upper case, before tryingto match it as given. If you write a provider and include versions of youralgorithm names in uppercase only, this JCE implementation will alwaysmatch a getInstance regardless of the case of the algorithm passed intothe getInstance method.<li>If the JCE API and the Provider were in a different class path, theclass loader being used sometimes failed to find classes for JCE Ciphers, etc.This has been fixed.<li>An error in the ASN.1 library was causing problems serialising Diffie-Hellman keys. This has been fixed.<li>The agreement package was left out of the j2me bat file. This has been fixed.<li>The BigInteger class for 1.0 and the j2me wasn't able to generate randomintegers (prime or otherwise). This has been fixed. <li>The BigInteger class would sometimes go into a death spiral if the any32nd bit of an exponent was set when modPow was called. This has been fixed. <li>Cipher.getInstance would treat "//" in a transformation as a single "/".This has been fixed.<li>PBEWithSHAAndIDEA-CBC was throwing an exception on initialisation. This hasbeen fixed.<li>The X509Name class in the asn1.x509 package wasn't initialising its localhash table when the hash table constructor was called. This has been fixed.</ul><h3>2.31.3 Additional Functionality</h3><ul><li>Added Elliptic Curve DSA (X9.62) - ECDSA - to provider and lightweightlibrary.<li>Added Elliptic Curve basic Diffie-Hellman to provider and lightweightlibrary.<li>Added DSA support to the provider and the lightweight library.<li>Added super class interfaces for basic Diffie-Hellman agreement classesto lightweight library.<li>The certificate generators now support ECDSA and DSA certs as well.</ul><h3>2.32.1 Version</h3>Release 1.03<h3>2.32.2 Defects Fixed</h3><ul><li>CFB and OFB modes when specified without padding would insist on inputbeing block aligned. When specified without padding CFB and OFB now behave in a compatible fashion (a doFinal on a partial block will yield just the data that couldbe processed).In short, it provides another way of generating cipher text the samelength as the plain text.</ul><h3>2.33.1 Version</h3>Release 1.02<h3>2.33.2 Defects Fixed</h3><ul><li>The RSA key pair generator occasionally produced keys 1 bit under therequested size. This is now fixed.</ul><h3>2.34.1 Version</h3>Release 1.01<h3>2.34.2 Defects Fixed</h3><ul><li>Buffered ciphers in lightweight library were not resetting correctlyon a doFinal. This has been fixed.</ul><h3>2.35.1 Version</h3>Release 1.0 <h3>2.35.2 Defects Fixed</h3><p><ul><li>JDK1.2 version now works with keytool for certificate generation.<li>Certificate toString method no longer throws a null pointer exceptionif a group [3] extension has not been added.<li>Under some circumstances the NullCipher would throw a NullPointerException,this has been fixed.<li>Under some circumstances CipherInputStream would throw a NullPointerException, this has been fixed.<li>OpenSSL/SSLeay private key encodings would cause an exception to be thrownby the RSA key factory. This is now fixed.<li>The Cipher class always used the default provider even when one was specified, this has been fixed.</ul><h3>2.35.3 Additional functionality</h3><p><ul><li>Argument validation is much improved.<li>An X509KeyUsage class has been added to the JCE class to make it easierto specify the KeyUsage extension on X.509 certificates.<li>The library now allows creation of version 1 certificates as well.</ul><h3>3.0 Notes</h3><p>The J2ME is only supported under Windows.<p>If you are trying to use the lightweight provider in a JDK 1.0 applet, youneed to change the package names for java.math.BigInteger, java.lang.IllegalStateException, and java.security.SecureRandom<p>The RSA test under JDK 1.0 and J2ME takes a while to run...</body></html>