Powerwash of chromebook by forced managed user
Reported by
18lucasb...@unionsd.org,
Mar 23 2017
|
|||
Issue descriptionThis bug allows for the powerwash of a chromebook. The user performs the bug by entering recovery mode and then turning on and off OS verification. This allows them to attempt developer mode. This, of course, is blocked. This then resets their chromebook, and for a short time allows them to powerwash with Ctrl+Alt+Shift+R before they select their language, internet connection, etc.
,
Mar 24 2017
Igor, would you take a look? Thanks.
,
Mar 24 2017
This works as intended. Anybody can powerwash a device while having physical control over it. More details: https://www.chromium.org/chromium-os/chromiumos-design-docs/powerwash
,
Mar 27 2017
This is for a forced managed user.
,
Mar 27 2017
I, as a middle school student, have a forced managed chromebook. Powerwashing as a forced managed user seems to be an unintentional feature.
,
Mar 27 2017
The feature is intentional for all the devices, regardless if it's enrolled or not. It is there to allow the user to reset the device to default state anytime. This might be useful when some memory corruption happened or device feels slow for example. For enrolled devices, admin has the option to set the device to be forcefully re-enrolled in case it's powerwashed/recovered, so the device remains managed.
,
Mar 27 2017
Ok. Thank you! |
|||
►
Sign in to add a comment |
|||
Comment 1 by 18lucasb...@unionsd.org
, Mar 23 2017