> I may have been mistaken. I remember that our xmlsec developer > needed a function to encrypt a piece of data that's not a symmetric > key using RSA PKCS #1, so we needed to give him a new function > because NSS only had a function to encrypt (wrap) a symmetric key > with RSA PKCS #1.
Using Google, I have found long discussion in libxmlsec mailing list about this, but they probably didn't used new function because they wanted compatibility with older releases of Mozilla/Firefox browsers. I think this is a good reason why you should add OAEP padding into NSS as soon as possible, and we (developers) will start using it when most Mozilla/Firefox browsers support it (include version of NSS that support OAEP). This might be a year or two after adding OAEP into NSS. _______________________________________________ mozilla-crypto mailing list [email protected] http://mail.mozilla.org/listinfo/mozilla-crypto
