New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 724169 link

Starred by 3 users
Status: Assigned
Owner:
teravest@chromium.org
Cc:
gwendal@chromium.org
█ cra...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocked on:
issue 718518
Blocking:
issue 845376



Sign in to add a comment

Expand secure_erase_file to support non-eMMC devices

Project Member Reported by teravest@chromium.org, May 18 2017 
The initial version of secure_erase_file is only set up to work with eMMC devices. We should expand this to support ATA and and NVMe as well. This will require some device dependent ioctls to send the correct sanitize commands.

Comment 1 by jclinton@chromium.org, Oct 25 2017 

On Eve/Pixelbook, 512GB NVMe, the time to enter developer mode is 44 minutes 56 seconds.

Comment 2 by teravest@chromium.org, Oct 27 2017

Cc: cra...@chromium.org

Comment 3 by hungte@chromium.org, Jun 13 2018

Blocking: 845376

Comment 4 by benhenry@chromium.org, Aug 3

Status: Assigned (was: Untriaged)
This bug has an owner, thus, it's been triaged. Changing status to "assigned".
►

Sign in to add a comment