Closed Bug 750455 Opened 13 years ago Closed 12 years ago

SecReview: (websms) WebSMS (or Messaging+)

Categories

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

task

Tracking

(blocking-basecamp:+)

RESOLVED FIXED
blocking-basecamp +

People

(Reporter: curtisk, Assigned: pauljt)

References

()

Details

(Whiteboard: [secreview complete][action items pending][score:56::Medium // Blocker])

SecReview tracking bug Actions regarding the review of the dependent bug should be tracked here.
I think we need to take a second pass at SMS, or at least review the changes that MMS will introduce.
Priority: -- → P1
assigning to Paul for second pass
Assignee: curtisk → ptheriault
Whiteboard: [secreview occured][action items pending] → [secreview complete][action items pending]
Risk/Priority Ranking Exercise https://wiki.mozilla.org/Security/RiskRatings Priority: 2 (P4) - Team Quarterly Goal Operational: 0 - N/A User: 0 - N/A Privacy: 3 - Major Engineering: 2 - Normal Reputational: 4 - Critical Priority Score: 24
Severity: normal → critical
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Priority: P1 → P4
Resolution: --- → FIXED
Whiteboard: [secreview complete][action items pending] → [secreview complete][action items pending][score:24::Medium]
I get a 56, making it a P2 mozilla initiative, which basecamp is. Risk/Priority Ranking Exercise https://wiki.mozilla.org/Security/RiskRatings Priority: 4 (P2) - Mozilla Initiative Operational: 0 - N/A User: 3 - Major Privacy: 3 - Major Engineering: 3 - Major Reputational: 5 - Blocker Priority Score: 56 The impact table is hard to use for reviews of new features. We don't really know what to say about it until after we take a look.
Priority: P4 → P2
Whiteboard: [secreview complete][action items pending][score:24::Medium] → [secreview complete][action items pending][score:56::Medium // Blocker]
blocking-basecamp: --- → +
I agree, I am trying to not take worst case or best case, but a middle likely case scenario. we can always re-evaluate as we get more info.
You need to log in before you can comment on or make changes to this bug.