New issue
Advanced search Search tips

Issue 816948 link

Starred by 1 user
Status: Fixed
Owner:
jorgelo@chromium.org
Closed: Mar 2018
Cc:
mnissler@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Task



Sign in to add a comment

Security: Write Chrome OS incident response doc

Project Member Reported by jorgelo@chromium.org, Feb 27 2018 
Title says it all.

Comment 1 by jorgelo@chromium.org, Feb 27 2018

Cc: mnissler@chromium.org
Components: OS>Systems
Labels: -Type-Bug -Pri-3 M-67 OS-Chrome Pri-2 Type-Task
Owner: jorgelo@chromium.org
Status: Started (was: startged)
Summary: Security: Write Chrome OS incident response doc (was: Security: Write Chrome OS incident response doc.)
Project Member

Comment 2 by bugdroid1@chromium.org, Mar 1 2018 

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/docs/+/a92c0599f40431c9841eca7e9c1fa21d0493d610

commit a92c0599f40431c9841eca7e9c1fa21d0493d610
Author: Jorge Lucangeli Obes <jorgelo@google.com>
Date: Thu Mar 01 16:33:22 2018

Comment 3 by jorgelo@chromium.org, Mar 1 2018 

Imma mark this fixed once the partner website ACLs are in place.

Comment 4 by jorgelo@chromium.org, Mar 30 2018

Status: Fixed (was: Started)
Alright, given that the document is written and we realized we don't need ACLs, this should be fixed.
►

Sign in to add a comment