Privacy/Features/mozCipherAddressbook: Difference between revisions

Jump to navigation Jump to search
m
clearing in prep for migration to new feature page format (will be done momentarily)
m (clearing in prep for migration to new feature page format (will be done momentarily))
Line 1: Line 1:
Once you have created your Feature page, please remove this paragraph and link to your page from the [[Features/Inbox|Features Inbox]], where a team will triage it and move it into the appropriate [[Features|Feature list]].  If you have any questions, please contact [[User:Dria|Deb]].


{| class="fullwidth-table"
|-
| style="font-weight: bold; background: #DDD;" | Feature
| style="font-weight: bold; background: #DDD;" | Status
| style="font-weight: bold; background: #DDD;" | ETA
| style="font-weight: bold; background: #DDD;" | Owner
|-
<section begin="status" />
| mozCipherAddressbookAPI
| {{StatusHealthy|status=Design and Implementation exists in an addon: DOMCrypt. (Needs porting)}}
| 2011-06-01
| David Dahl
<section end="status" />
|-
|}
== Summary ==
A simple API for exchanging public keys via web page metatags as an enhancement to the DOMCryptAPI (mozCipher), see: [[Privacy/Features/DOMCryptAPI]]
== Team ==
* '''Feature Manager''': ''David Dahl''
* '''Lead Developer''': David Dahl
* '''Product Manager''': Dietrich Alaya
* '''QA''': Juan Beccera
* '''UX''': Limi
* '''Accessibility''':
* '''Security''': Sid Stamm
* '''Privacy''': Sid Stamm
== Release 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. 
== Next Steps & Open Issues ==
Port the existing synchronous API over to an asynchronous API
== Related Bugs & Dependencies ==
{{bug|657432}}
== Risks ==
None on the radar at this point. Will update.
== 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):
window.mozCipher.getAddressbook();
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.
== Designs ==
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]
== Test Plans ==
TBD
== Goals ==
As simple as possible mechanism for web users to discover and save public keys as a helper for the DOMCryptAPI
== Non-Goals ==
Any kind of key management UI or toolkit
== Other Stuff ==
== Legend ==
{| class="fullwidth-table"
|-
| {{StatusHealthy|status=&nbsp;}}
| Healthy: feature is progressing as expected.
|-
| '''ETA'''
| 2011-08-01
|}
__NOTOC__
[[Category:Features]]
[[Category:Firefox]]
[[Category:Platform]]
[[Category:Services]]
[[Category:Mobile]]
canmove, Confirmed users, Bureaucrats and Sysops emeriti
6,906

edits

Navigation menu