Closed Bug 750458 Opened 13 years ago Closed 12 years ago

SecReview: implement navigator.mozApps

Categories

(mozilla.org :: Security Assurance: Review Request, task, P2)

Product:
mozilla.org
Component:
Security Assurance: Review Request
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: curtisk, Assigned: dchanm+bugzilla)

References

Details

(Whiteboard: [completed secreview][start 2012-10-30][target 2012-10-30][score:64::High][code review])

SecReview tracking bug Actions regarding the review of the dependent bug should be tracked here.
:dveditz has some concerns in this area, please get together with him to discuss how we want to go about reviewing the code here
Risk/Priority Ranking Exercise https://wiki.mozilla.org/Security/RiskRatings Priority: 2 (P4) - Team Quarterly Goal Operational: 0 - N/A User: 2 - Normal Privacy: 3 - Major Engineering: 2 - Normal Reputational: 1 - Minor Priority Score: 16
Severity: normal → major
Priority: -- → P4
Whiteboard: [pending secreview] → [pending secreview][start yyyy-mm-dd][target yyyy-mm-dd][score:16::Low][code review]
if bug 697383 is marked sec-review+ by David does that mean this bug should be resolved? I'm pretty sure a priority score of "low" isn't right for this feature -- it's important, visible, and if things go wrong it's pretty bad.
Yes, we can close off this bug since the sec-review action was attached to the feature bug. Here is the updated risk rating. I believe the old score was from a different formula Risk/Priority Ranking Exercise https://wiki.mozilla.org/Security/RiskRatings Priority: 4 (P2) - Mozilla Initiative Operational: 0 - N/A User: 5 - Blocker Privacy: 3 - Major Engineering: 5 - Blocker Reputational: 3 - Major Priority Score: 64
Severity: major → blocker
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Priority: P4 → P2
Resolution: --- → FIXED
Whiteboard: [pending secreview][start yyyy-mm-dd][target yyyy-mm-dd][score:16::Low][code review] → [completed secreview][start 2012-10-30][target 2012-10-30][score:64::High][code review]
You need to log in before you can comment on or make changes to this bug.