Oops. I reread what I wrote and now I am confused. Maybe you are right. In developer mode, self signed images work. But I will leave the post.
--------------------------------
If you are talking about developer mode, Yes. I am pretty sure they intend to have that option in production devices.
No. I think, even in developer mode the boot process checks for google signature.
From their site;
"The first time a Chrome Notebook boots in Developer Mode after leaving Normal Mode it will:
- Show a scary warning that its software cannot be trusted, since verified boot is disabled (press Ctrl-D or wait 30 seconds to dismiss).
- Erase all personal data on the "stateful partition" (i.e., user accounts and settings - no worries, though, since all data is in the cloud!).
Make you wait between 5 and 10 minutes to while it erases the data.
- Boot from any self-signed image on its SSD, negating the security of verified boot.
--------------------------------
If you are talking about developer mode, Yes. I am pretty sure they intend to have that option in production devices. No. I think, even in developer mode the boot process checks for google signature.
From their site; "The first time a Chrome Notebook boots in Developer Mode after leaving Normal Mode it will: - Show a scary warning that its software cannot be trusted, since verified boot is disabled (press Ctrl-D or wait 30 seconds to dismiss). - Erase all personal data on the "stateful partition" (i.e., user accounts and settings - no worries, though, since all data is in the cloud!). Make you wait between 5 and 10 minutes to while it erases the data. - Boot from any self-signed image on its SSD, negating the security of verified boot.
https://sites.google.com/a/chromium.org/dev/chromium-os/deve...