canmove, Confirmed users
640
edits
Security/Bug Approval Process: Difference between revisions
Jump to navigation
Jump to search
m
Convert examples into a bullet list so items don't get lost in a long sentence
No edit summary |
m (Convert examples into a bullet list so items don't get lost in a long sentence) |
||
| Line 1: | Line 1: | ||
==Purpose: don't 0-day ourselves== | ==Purpose: don't 0-day ourselves== | ||
People watch our check-ins. | People watch our check-ins. They may be able to start exploiting our users before we can get an update out to them if | ||
* the patch is an obvious security fix (bounds check, kungFuDeathGrip, etc.) | |||
* the check-in comment says "security fix" or includes trigger words like "exploitable", "vulnerable", "overflow", "injection", "use after free", etc. | |||
* comments in the code mention those types of things or how someone could abuse the bug | |||
* the check-in contains testcases that show exactly how to trigger the vulnerability | |||
==Principle: assume the worst== | ==Principle: assume the worst== | ||