Martin Paljak wrote: > On Sep 21, 2010, at 12:48 PM, Michael Ströder wrote: >> The keys should be sent from the web app to the browser protected via Shared >> Secret negotiated before. So we would need to access a RSA API functions for >> encryption/decryption from Javascript passing in the RSA key blob (probably >> PKCS#1). >> >>> Do you mean using the keys available via NSS? >> >> The keys are definitely not stored in a key-store accessible via PKCS#11. >> >>> There is signText() but that's not really useful IMHO [1] >>> >>> [1] https://developer.mozilla.org/en/JavaScript_crypto >> >> Yes, I know. Unfortunately not applicable in our case. >> >> Implementing and rolling out an extension is also not an option... > > Without knowing your use case and requirements I still think a Java applet > would be the easiest option. Do you have some performance tables for > javascript based crypto libraries? I checked http://www.ohdave.com/rsa/ and > with a 1024b key verification worked without any noticeable delay.
I already had played with this demo and the Seamonkey browser raised a pop-up window about possibly blocking Javascript code. Not an option for a user-friendly application. (on a notebook with 2,4 GHz dual core CPU) Ciao, Michael. -- dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
