User Tools

Site Tools


This is an old revision of the document!

Table of Contents


  • people can fully use Chromium OS without needing a Google login (fine);
  • plan to give SSO experience at OpenID relying parties;
  • user name will be hashed HASH(salt|| Web-based user name may contain characters that are not safe for use on the file system (nice side effect for the security).


The image encryption key for the dm-crypt device is generated randomly during setup using the randomness generator provided by the kernel, and if supported, seeded by a hardware random number generator. It is then encrypted with a partial cryptographic hash derived from the user's Google Accounts password and stored with the encrypted image on the underlying file system. On login, the encryption key is decrypted, and the encrypted image is mounted over the user's home directory. If the user's password changes, the image encryption key is re-encrypted with a new weak hash generated from the new passphrase. There are still some outstanding issues around what happens if a user changes her password from a non-Chromium OS machine….


  • Google Chromium OS applications for maximum security;
  • possible to install applications from external sources (like Android)
  • all HTML5-enabled web applications.
chromium-os.1291675999.txt.gz · Last modified: 2010/12/06 23:53 by cedric