//components/mus/public/interfaces/*.mojom needs a security review |
|||||||||||||||
Issue descriptionThese interfaces don't appear to have gone through security review. Marking ReleaseBlock-Stable to be on the safe side for now.
,
May 14 2016
,
May 16 2016
[Bulk edit] Release blockers need OS set. Looks like all of these are applicable for OS-All, correct if required.
,
May 17 2016
,
Jun 1 2016
This issue is set as M52 Release block Stable. Is there anything which needs to to be taken care in M52? Please resolve ASAP.
,
Jun 6 2016
Code is not turned on in production. It is a release blocker for mus but mus is not released.
,
Jun 21 2016
Bulk edit: swapping issues for mojo reviews back to Security_Impact-Stable. We're adding a sheriffbot rule to automatically remove release block labels from Security_Impact-None bugs, but in this case I think they make sense. These issues for audits/reviews tend to be a bit awkward to triage.
,
Jun 22 2016
,
Jun 24 2016
,
Jun 25 2016
,
Jun 25 2016
Dialling down the security impact based on #6
,
Jun 26 2016
,
Jul 6 2016
,
Jul 6 2016
,
Jul 6 2016
,
Aug 10 2016
Removing from the security sheriff queue. |
|||||||||||||||
►
Sign in to add a comment |
|||||||||||||||
Comment 1 by dcheng@chromium.org
, May 14 2016