This is an old revision of the document!

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||user@domain.com). Web-based user name may contain characters that are not safe for use on the file system (nice side effect for the security).

Security

cgroups http://www.kernel.org/doc/Documentation/cgroups/cgroups.txt Actually Chromium runs Linux 2.6.35;
cached data http://www.chromium.org/chromium-os/chromiumos-design-docs/protecting-cached-user-data#Appendix_D_Designs_considered
Suspending to RAM works already quite well with dm-crypt:
- according to Google no concrete solutions against sophisticated attacks like Cold Boot Attacks on Encryption Keys http://www.chromium.org/chromium-os/chromiumos-design-docs/protecting-cached-user-data#TOC-Suspending-to-RAM, http://citp.princeton.edu/memory/
verified boot crypto specification:
- developer builds do not use a verified boot;
- the TPM is used as secure non-volatile storage for preventing key rollback attacks (not for the encryption);
- Google plan is to use a 8192-bit RSA key with SHA-512 for the root key signatures (NIST recommends the use of RSA 2048/SHA-256 or higher as the signature algorithm for use after 12/31/2010);
- signin keys will change offently (Google plan to use 1024-bit RSA keys which provides a good speed/performance trade-off);

Applications