DOMCryptAPI (a Crypto API in the DOM)

RESOLVED WONTFIX

Status

mozilla.org
Security Assurance: Review Request
RESOLVED WONTFIX
6 years ago
5 years ago

People

(Reporter: curtisk, Unassigned, NeedInfo)

Tracking

Details

(Whiteboard: [pending secreview][Fx], URL)

Who is/are the point of contact(s) for this review?
    
Please provide a short description of the feature / application (e.g. problem solved, use cases, etc.):
    
Please provide links to additional information (e.g. feature page, wiki) if available and not yet included in feature description:
    
Does this request block another bug? If so, please indicate the bug number This review will be scheduled amongst other requested reviews. What is the urgency or needed completion date of this review?

Please answer the following few questions: (Note: If you are asked to describe anything, 1-2 sentences shall suffice.)

Does this feature or code change affect Firefox, Thunderbird or any product or service the Mozilla ships to end users?

Are there any portions of the project that interact with 3rd party services?

Will your application/service collect user data? If so, please describe 

If you feel something is missing here or you would like to provide other kind of feedback, feel free to do so here (no limits on size):

Desired Date of review (if known from https://mail.mozilla.com/home/ckoenig@mozilla.com/Security%20Review.html) and whom to invite.
Assignee: nobody → curtisk
Status: NEW → ASSIGNED
assigning to :ddahl, so they can get these answered when ready
Assignee: curtisk → ddahl
Whiteboard: [pending secreview][needs info]
Flags: needinfo?(ddahl)
Whiteboard: [pending secreview][needs info] → [pending secreview]
Whiteboard: [pending secreview] → [pending secreview][Fx]

Updated

5 years ago
Assignee: ddahl → nobody
Flags: needinfo?(ddahl)
David:  Is there any work to be done?  Should we close this bug as invalid?
Flags: needinfo?(david)
wontfix to match the feature bug.
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.