Clarify security bug labeling guidelines w.r.t. visibility |
||
Issue descriptionWe already have https://cs.chromium.org/chromium/src/docs/security/security-labels.md, but as a follow-up to a recent accidental leak, we should: 1. Clarify advice on setting view restrictions a bit 2. Clearly document sheriffbot interactions 3. Figure out whether we can have sheriffbot leave messages in its update that make it easier for uninitiated people to understand what's going on.
,
Dec 7 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/ec018258ce725cedcb057ea1cdc520f86de40dc7 commit ec018258ce725cedcb057ea1cdc520f86de40dc7 Author: Mattias Nissler <mnissler@chromium.org> Date: Thu Dec 07 20:46:19 2017 Expand documentation on security labels. Specifically, describe the sheriffbot rules that change security relevant labels and the rationale behind them. BUG= chromium:784384 TEST=None Change-Id: Ie782f5b2339385a4bb88400b174009835be65c6c Reviewed-on: https://chromium-review.googlesource.com/768732 Commit-Queue: Mattias Nissler <mnissler@chromium.org> Reviewed-by: Chris Palmer <palmer@chromium.org> Cr-Commit-Position: refs/heads/master@{#522539} [modify] https://crrev.com/ec018258ce725cedcb057ea1cdc520f86de40dc7/docs/security/security-labels.md
,
Apr 24 2018
|
||
►
Sign in to add a comment |
||
Comment 1 by awhalley@google.com
, Nov 17 2017