Closed Bug 1071206 Opened 11 years ago Closed 11 years ago

Restore mwu's access to Socorro PII

Categories

(Socorro :: General, task)

x86_64
Linux
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: kairo, Assigned: lonnen)

Details

mwu got access to Socorro PII in bug 612352, but as he didn't log in via Persona before we migrated to the new permissions, we randomly removed his access (he's listed in attachment 8342491 [details], which lists everyone to whom that happened, many of them we did restore in the beginning phase without bureaucracy attached). Apparently we now require to run through the whole process again. He asked me for this in #developers today so I'm filing the bug for it.
hema -- I need your ack that MWU needs access to crash report PII MWU -- It's been a while so I'll need you to ack that you understand and will abide by the following policies: * Crash dumps contain memory contents, and may contain private user data. * Only access dumps as necessary. * Keep them securely on Mozilla hardware. * When finished with a dump, delete it (within 30 days) * Do not share personal data from the dump publicly (on bugzilla, irc, etc) * Do not share personal data with non-employees, including partner organizations, without consultation and explicit permission from Lonnen(me). A signed NDA and other arrangements will be required of the other organization. * It is fine to share stack traces, analysis, and other non-personal data * Access is conditional on employment and will be revoked upon departure from Mozilla
Flags: needinfo?(mwu)
Flags: needinfo?(hkoka)
Ack for Mike Wu's access to crash report PII
Flags: needinfo?(hkoka)
Ack to the crash dump policy.
Flags: needinfo?(mwu)
Granted. You now have permissions to view PII, rawdumps, exploitability info, and timeouts on your requests have been raised so you can run more complicated search queries. Happy hacking.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.