3 ms·
This is trivially avoided by adding a setup password. Additionally, the system could display a hash of the keystore at boot - AIUI, Purism has worked on somethi
by 0815test 8y ago
This is trivially avoided by adding a setup password. Additionally, the system could display a hash of the keystore at boot - AIUI, Purism has worked on something like that.
- saagarjha 8y agoThis doesn't help ordinary users who aren't going to check the hash at boot.
- 0815test 8y agoOK, so we're talking about users who have unlocked the system themselves and enrolled a user key onto it, but aren't going to notice if it changes unexpectedly? Suuure.
- saagarjha 8y agoNo, you also have to include users who would like to run "stock" Chrome OS and continue trusting Google's keys. How do you protect them?