Vishal
--- Begin Message ---Thanks for the notification. I note the document also specifies a similar convention for PSS signature mechanisms. I've only recently started looking at JDK 1.5 - there are a few other things like the elliptic curve classes which we are looking at supporting as well hadn't gotten to noticing the naming conventions...In the case of the BC provider "OAEPPadding" represents the default settings for the RSAES-OAEP-params object described in the ASN.1 module for PKCS#1, or more simply "OAEPWithSHA1andMGF1Padding" under the new convention. The reason for the current naming is that "AOEPPadding" has been in the provider for over four years, well before any convention was proposed, also well before anyone really considered anything other than the default... So, if you need a temporary workaround do a: Provider bc = Security.getProvider("BC"); bc.put("Alg.Alias.Cipher.RSA/NONE/OAEPWithSHA1AndMGF1Padding","RSA/OAEP"); or if you have a compliance issue stick with OAEPWithSHA1AndMGF1Padding in the other provider and everything should behave. The new naming conventions will be available in the next release. We will continue to support "OAEPPadding" as well. Regards, David On Tue, 2004-10-05 at 12:33, Vishal Mahajan wrote: > [Re-sending with subject] > > Hi, > > The bouncy castle JCE provider jars do not seem to follow the standard > JCE naming as described in [1]. Specifically the problem is with Optimal > Asymmetric Encryption Padding, whose name should follow the format - > "OAEPWith<digest>And<mgf>Padding", but BC provider seems to uses > "OAEPPADDING" for this padding. > > Vishal > > [1] http://java.sun.com/j2se/1.5.0/docs/guide/security/CryptoSpec.html#AppA >
--- End Message ---
