canmove, Confirmed users
1,537
edits
No edit summary |
No edit summary |
||
| (8 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{FeatureStatus | {{FeatureStatus | ||
|Feature name= | |Feature name=DOMCrypt Internal API | ||
|Feature stage= | |Feature stage=On hold | ||
|Feature status=In progress | |Feature status=In progress | ||
|Feature version=N/A | |Feature version=N/A | ||
|Feature health=OK | |Feature health=OK | ||
|Feature status note=Needs a new owner | |||
}} | }} | ||
{{FeatureTeam | {{FeatureTeam | ||
|Feature product manager=Sid Stamm | |Feature product manager=Sid Stamm | ||
|Feature security lead=Brian Smith | |Feature security lead=Brian Smith | ||
|Feature privacy lead=Sid Stamm | |Feature privacy lead=Sid Stamm | ||
| Line 21: | Line 20: | ||
}} | }} | ||
{{FeaturePageBody | {{FeaturePageBody | ||
|Feature open issues and risks= | |Feature open issues and risks=The content DOM API that this feature will support should obey private browsing mode, but also integrate well with PSM/NSS, in which case the keystore does not know about Private Browsing. We may need to tie the key storage to Places or something new. | ||
|Feature overview=DOMCryptInternalAPI is the PSM code that will generate keypairs, sign, verify, hash, hmac, encrypt and decrypt data. The scriptable interface will reside outside of PSM, consuming this API and providing a simpler abstraction for DOMCrypt, a WebAPI currently being standardized by the W3C via the Web Cryptography Working Group: http://www.w3.org/2012/webcrypto/. This API will also be useful to extension developers and the AddonSDK | |Feature overview=DOMCryptInternalAPI is the PSM code that will generate keypairs, sign, verify, hash, hmac, encrypt and decrypt data. The scriptable interface will reside outside of PSM, consuming this API and providing a simpler abstraction for DOMCrypt, a WebAPI currently being standardized by the W3C via the Web Cryptography Working Group: http://www.w3.org/2012/webcrypto/. This API will also be useful to extension developers and the AddonSDK | ||
|Feature users and use cases=* DOMCrypt's DOM bindings ( W3C Web Crypto WG ) will consume this API for all crypto-related functionality | |Feature users and use cases=* DOMCrypt's DOM bindings ( W3C Web Crypto WG ) will consume this API for all crypto-related functionality | ||
| Line 81: | Line 80: | ||
const unsigned long ALGORITHM_RSA = 0; | const unsigned long ALGORITHM_RSA = 0; | ||
const unsigned long ALGORITHM_DSA = 1; | |||
void SigGenerateKeyPair(in unsigned long aKeySizeInBits, | void SigGenerateKeyPair(in unsigned long aKeySizeInBits, | ||
| Line 113: | Line 113: | ||
</pre> | </pre> | ||
* There is also the need for a symmetric encryption API, perhaps based on DHKE to specify | * There is also the need for a symmetric encryption API, perhaps based on DHKE to specify | ||
|Feature security review=Brian Smith, Kai Engert and Wan-Teh Chang will be asked for review and super review | |||
|Feature privacy review=The privacy team will review this API for potential data leaks, fingerprinting, etc. | |||
|Feature localization review=N/A | |||
|Feature accessibility review=Undetermined | |||
|Feature qa review=Undetermined | |||
|Feature operations review=N/A? | |||
}} | }} | ||
{{FeatureInfo | {{FeatureInfo | ||
|Feature priority= | |Feature priority=Unprioritized | ||
|Feature theme= | |Feature theme=Security Leadership | ||
|Feature roadmap=Security | |Feature roadmap=Security | ||
|Feature secondary roadmap=Privacy | |Feature secondary roadmap=Privacy | ||
| Line 124: | Line 130: | ||
{{FeatureTeamStatus | {{FeatureTeamStatus | ||
|Feature engineering status=Under development | |Feature engineering status=Under development | ||
|Feature engineering notes=The initial patch is being worked on via {{bug|649154}} | |Feature engineering notes=The initial patch is being worked on via {{bug|649154}} , additional bugs are blocked by {{bug|649154}} | ||
|Feature security status=sec-review-active | |||
|Feature security health=Assigned | |||
|Feature security notes=we want to have bsmith look at this | |||
}} | }} | ||