----- Original Message ----- > From: "Benjamin Smedberg" <benja...@smedbergs.us> > To: "Brian Smith" <bsm...@mozilla.com> > Cc: "dev-platform" <dev-platf...@lists.mozilla.org>, "mozilla's crypto code > discussion list" > <dev-tech-crypto@lists.mozilla.org> > Sent: Wednesday, January 18, 2012 11:06:21 AM > Subject: Re: Removal of NSS and/or NSPR from the API exposed to addons
> > 3. Help out with the DOMCrypt effort that ddahl is leading, which > > will create a W3C-standardized Javascript API for cryptography for > > *web* applications. I suspect it would be non-trivial, but > > possible, to expose the DOMCrypt API to extensions. I suspect that > > this would replace APIs from #1 and #2 above. > I tend to think that extensions would get this basically "for free" > because they have access to the DOM. Indeed they will. There is also (possibly going to be) a privileged JS API that allows for more flexibility as the DOM API will tie all crypto operations to the current domain. I can see some extensions needing to ignore this limitation. David -- dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
