Closed Bug 754738 Opened 12 years ago Closed 12 years ago

[Security Review] B2G Gaia - Communications / Contacts

Categories

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

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

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: pauljt, Assigned: st3fan)

References

(
URL
)

Details

(Keywords: meta, Whiteboard: [Score:64:High])

Review of the gaia contacts app (currently part of the dialer app: http://dialer.gaiamobile.org/)
Priority: -- → P1
Assignee: nobody → ptheriault
Component: Security Assurance → Security Assurance: Review Request
Priority: P1 → P2
Risk/Priority Ranking Exercise https://wiki.mozilla.org/Security/RiskRatings Priority: 4 (P2) - Mozilla Initiative Operational: 0 - N/A User: 4 - Critical Privacy: 4 - Critical Engineering: 4 - Critical Reputational: 4 - Critical Priority Score: 64
Whiteboard: [Score:64:High]
Assignee: ptheriault → fbraun
Depends on: 828751
I think I'm done with the sec review. From a privacy perspective, I can say that personal data is mostly read *from* facebook and not pushed back. This is good :) The only issue I found is a minor thing, but I filed it as bug 828751. This is my first sec review for a b2g app and I am still not 100% sure what to look for. So I'd appreciate it if somebody else might take another look. Except for this, I'm done now.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Depends on: 835983
Most of the code has changed, we might need to look again
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee: fbraun → sarentz
Summary: [Security Review] B2G Gaia - Contacts → [Security Review] B2G Gaia - Communications / Contacts
Depends on: 847417
Depends on: 847649
Depends on: 847650
No longer depends on: 835983
I'm done with this. Bugs filed. See notes at https://wiki.mozilla.org/Security/Reviews/Gaia/Contacts
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.