chromium-os
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
chromium-os [2010/12/06 23:53] cedric |
chromium-os [2010/12/06 23:57] cedric |
||
|---|---|---|---|
| Line 16: | Line 16: | ||
| * signin keys will change offently (Google plan to use 1024-bit RSA keys which provides a good speed/ | * signin keys will change offently (Google plan to use 1024-bit RSA keys which provides a good speed/ | ||
| + | |||
| + | ===== Partition encryption ===== | ||
| + | Each user is allocated one encrypted image file that can grow to fill the free space on its disk partition. The image file is stored in a directory specific to the user using a hash of the user name with a salt value. The image itself is a sparse file that is attached to the system through a loop device. Using the device mapper subsystem, a virtual, encrypting block device, dm-crypt, is layered on top of the loop device. | ||
| // | // | ||
chromium-os.txt ยท Last modified: 2010/12/14 22:37 by cedric
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
