On 11/20/2013 2:11 PM, fma spew wrote:
The prompt part is not needed to be provided by WebCrypto. In the latest
releases, the prompt part has been taken care of our plugin. However, in
our new prototype, the scripting UI part (Dojo) will take care of it.
I expect that the browser will need to mediate access to the signing
token: otherwise any website could sign anything. So whether it's part
of WebCrypto or a separate spec, we will absolutely need to ask the user
to choose a certificate and give a particular website access to it for
signing purposes.
I need to check one more thing. We've heard of js-ctypes. However, you
mostly talk about WebCrypto. Our js-ctypes knowledge is pretty limited.
JS ctypes is a technology for Firefox extensions to interface with DLLs.
If you want to deploy a Firefox extension, you could do that using
either NPAPI or ctypes, although NPAPI might be safer.
--BDS
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
