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.

holding on to this as we may have implications for this in B2G

:pauljt - Do we need to keep this or is it obsolete?

This is something to look at well down the road. Given that this is 'wont-fix' for linux, I dont think it is priority for b2g. At least definitely not for basecamp.

Risk/Priority Ranking Exercise https://wiki.mozilla.org/Security/RiskRatings Priority: 1 (P5) - Age Operational: 4 - Critical User: 4 - Critical Privacy: 4 - Critical Engineering: 2 - Normal Reputational: 4 - Critical Priority Score: 14

I'm closing this as I don't think this relates to FirefoxOS, and afaict, that is the only reason it is still open.