- From: Simon Heckmann <simon@simonheckmann.de>
- Date: Sat, 21 May 2011 00:44:52 +0200
Why does it only handle asymmetric encryption? Something to encrypt/decrypt data with e.g. AES would be nice as well! Kind regards, Simon Heckmann Am 20.05.2011 um 20:45 schrieb Adam Barth <w3c at adambarth.com>: > Why window.cipher and not just window.crypto? > > Adam > > > On Fri, May 20, 2011 at 8:04 AM, David Dahl <ddahl at mozilla.com> wrote: >> Hello WHATWG members, >> >> With user control and privacy in mind, I have created a spec and an implementation for an easy to use cryptography API called DOMCrypt. This API will provide each web browser window with a 'cipher' property that facilitates: >> >> * asymmetric encryption key pair generation >> * public key encryption >> * decryption >> * signature generation >> * signature verification >> * hashing >> * easy public key discovery via meta tags >> >> I have created a Firefox extension that implements all of the above, and am working on an experimental patch that integrates this API into Firefox. >> >> The draft spec is here: https://wiki.mozilla.org/Privacy/Features/DOMCryptAPISpec/Latest >> >> The project originated in an extension I wrote, the home page is here: http://domcrypt.org >> >> The source code for the extension is here: https://github.com/daviddahl/domcrypt >> >> The Mozilla bugs are here: >> https://bugzilla.mozilla.org/show_bug.cgi?id=649154 >> https://bugzilla.mozilla.org/show_bug.cgi?id=657432 >> >> You can test the API by installing the extension hosted at domcrypt.org and addons.mozilla.org, and going to http://domcrypt.org >> >> Best Regards, >> >> David Dahl >> >> Firefox Engineer, Mozilla Corp. >>
Received on Friday, 20 May 2011 15:44:52 UTC