Re:An Engineer's take on Chrome OS
by ConstantineXVI on Tuesday April 02, 2013 @10:11PM
(#5483756)
Developer mode's designed[0] to avoid using it to bypass CrOS's security. The relevant points:
* the 5-minute wipe both hinders access to the owner's data and makes it unlikely the OS can be replaced with a malicious variant without being caught in the act
* the warning screens ensure the owner's aware they're in devmode
* Hiding the Ctrl-D bypass makes it appear the only option is recovery, you won't know about it unless you've enabled devmode yourself.
[0] http://dev.chromium.org/chromium-os/chromiumos-design-docs/d...
What's scary about it? It's the bootloader telling you it's in dev mode and not checking signatures.
And yes it sits there for 30 seconds. Ctrl-d boots immediately from internal storage and Ctrl-u from USB or SD.
I'm not sure why you need to wipe when switching between dev and recovery mode. Maybe it's to stop you booting an alternate OS and getting at ChromeOS user data without a password?
Based on 10 seconds of thinking, maybe they want to prevent you from installing a suid binary in your home directory when in developer mode and then somehow running it in the regular mode.
Why would you need to wipe the main partition in order to be able to dual boot? Also, I hear that this scary screen comes up every time you boot for 30 seconds unless you press Ctrl-D everytime.
http://liliputing.wpengine.netdna-cdn.com/wp-content/uploads...