Closed
Bug 551745
Opened 16 years ago
Closed 8 years ago
things needed to avoid leaking of security patches and tipping our hand to evil doers prematurely.
Categories
(Firefox :: Security, defect)
Firefox
Security
Tracking
()
RESOLVED
DUPLICATE
of bug 1136954
People
(Reporter: chofmann, Unassigned)
References
Details
(Keywords: meta, sec-other, Whiteboard: [sg:nse meta])
malware developers have the ability to watch our source file checkins and get a head start in creating exploits before before the patches are released in maintenece releases. a paper released summer 2010 will outline steps to identify security patches sooner and weed out security problems from the high volume of general patches landing on the trunk. We need a better system for keeping the patches hidden while making progress on review and testing, then manage risk and reduce exposure time during public beta testing and deployment to the geneneral firefox user base.
this is a tracking bug for all the pieces needed to improve security patch hiding, increase testing while the patches are under development, and reduce pre-release risk and exposure time.
| Reporter | ||
Comment 1•16 years ago
|
||
more details on the overall plan are at https://securitywiki.mozilla.org/SourceLeakRiskReductionPlan
| Reporter | ||
Comment 2•16 years ago
|
||
we will need to complete all the dependency bugs by the end of q2 to stay ahead of the release of the research paper, so this needs to get good attention in q2 goal setting.
Updated•16 years ago
|
OS: Mac OS X → All
Hardware: x86 → All
Version: 3.5 Branch → unspecified
Updated•11 years ago
|
Group: core-security → firefox-core-security
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Updated•4 years ago
|
Group: firefox-core-security
You need to log in
before you can comment on or make changes to this bug.
Description
•