chromium-os
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
chromium-os [2010/12/06 23:16] – cedric | chromium-os [2010/12/06 23:49] – cedric | ||
---|---|---|---|
Line 3: | Line 3: | ||
* people can fully use Chromium OS without needing a Google login (fine); | * people can fully use Chromium OS without needing a Google login (fine); | ||
* plan to give SSO experience at OpenID relying parties; | * 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 ====== | ====== Security ====== | ||
Line 8: | Line 9: | ||
* cached data http:// | * cached data http:// | ||
* Suspending to RAM works already quite well with dm-crypt: | * Suspending to RAM works already quite well with dm-crypt: | ||
- | * according to Google no solutions against sophisticated attacks like Cold Boot Attacks on Encryption Keys http:// | + | * according to Google no concrete |
* verified boot crypto specification: | * verified boot crypto specification: | ||
* developer builds do not use a verified boot; | * developer builds do not use a verified boot; | ||
Line 19: | Line 20: | ||
* Google Chromium OS applications for maximum security; | * Google Chromium OS applications for maximum security; | ||
* possible to install applications from external sources (like Android) | * possible to install applications from external sources (like Android) | ||
- | * all HTML5 applications | + | * all HTML5-enabled web applications. |
chromium-os.txt · Last modified: 2010/12/14 22:37 by cedric