canmove, Confirmed users, Bureaucrats and Sysops emeriti
6,906
edits
Privacy/Features/mozCipherAddressbook: Difference between revisions
Privacy/Features/mozCipherAddressbook (view source)
Revision as of 01:41, 14 July 2011
, 14 July 2011no edit summary
m (clearing in prep for migration to new feature page format (will be done momentarily)) |
mNo edit summary |
||
| Line 1: | Line 1: | ||
{{FeatureStatus | |||
|Feature name=mozCipherAddressbookAPI | |||
|Feature stage=Planning | |||
|Feature health=OK | |||
|Feature status note=Design and Implementation exists in an addon: DOMCrypt. (Needs porting) | |||
}} | |||
{{FeatureTeam | |||
|Feature product manager=Chris Blizzard | |||
|Feature feature manager=Dietrich Ayala | |||
|Feature lead engineer=David Dahl | |||
|Feature security lead=Sid Stamm | |||
|Feature privacy lead=Sid Stamm | |||
|Feature qa lead=Juan Becerra | |||
|Feature ux lead=Alex Limi | |||
}} | |||
{{FeaturePageBody | |||
|Feature overview=A simple API for exchanging public keys via web page metatags as an enhancement to the DOMCryptAPI (mozCipher), see: [[Privacy/Features/DOMCryptAPI]]. | |||
Goals: As simple as possible mechanism for web users to discover and save public keys as a helper for the DOMCryptAPI. | |||
|Feature users and use cases=DOMCrypt (see [[Privacy/Features/DOMCryptAPI]] is a public key crypto API, which is useful as-is, but to enhance the user experience, a simple method to collect and store your contact's public keys would make DOMCrypt a bit more powerful. This simple API adds to window.mozCipher (which is provided by DOMCrypt): | |||
<code>window.mozCipher.getAddressbook();</code> | |||
It also adds a browser-side notificationbar that is displayed when a "addressbook-entry" meta tag is encountered. This notificationbar asks the user to save or ignore the "contact entry". This is a very simple way for endusers to exchange public keys and is presented in a language that is easily understood. Users need each other's addressbook entry to exchange private message data. This simplifies the nomenclature greatly, which will help bring more user control and privacy to users who care to exchange data on the web in a more secure manner. | |||
|Feature requirements=Parsing the DOM on idle to discover "addressbook-entry" meta tags would make the most sense - there is a little bit of research to do here on perf. | |||
|Feature non-goals=Any kind of key management UI or toolkit. | |||
|Feature functional spec=The existing implementation is here: [https://github.com/daviddahl/domcrypt/blob/master/extension/domcrypt/content/addressbookManager.js] | |||
A demo can be found here: [http://domcrypt.org] | |||
|Feature implementation plan===== Next Steps & Open Issues ==== | |||
Port the existing synchronous API over to an asynchronous API | |||
==== Related Bugs ==== | |||
{{bug|657432}} | |||
}} | |||
{{FeatureInfo | |||
|Feature priority=P3 | |||
|Feature roadmap=Privacy | |||
|Feature list=Platform | |||
|Feature engineering team=Platform | |||
}} | |||
{{FeatureTeamStatus}} | |||