- 14 Mar, 2010 3 commits
-
-
San Mehat authored
Change-Id: Ia57da8ee177453a601a23d965c2b4f16b6de46e5 Signed-off-by:
San Mehat <san@google.com>
-
San Mehat authored
Change-Id: I74aa63ff9f9bc32bd871e6c53ab50b6baf79e650 Signed-off-by:
San Mehat <san@google.com>
-
San Mehat authored
- Fix issue where container-names > 64 bytes were getting truncated in the kernel. lo_name is only 64 bytes in length, so we now hash the container id via md5 - Add 'dump' command to dump loop and devicemapper status - Add 'debug' command to enable more detailed logging at runtime - Log vold IPC arguments (minus encryption keys) - Fix premature return from Loop::lookupActive() and friends Change-Id: I0e833261a445ce9dc1a8187e5501d27daba1ca76 Signed-off-by:
San Mehat <san@google.com>
-
- 10 Mar, 2010 1 commit
-
-
San Mehat authored
Also handles an issue where NPARTS=0 on a disk change uevent Change-Id: I77c56f177dc65df91468bbd7d5fe1889db414d7a Signed-off-by:
San Mehat <san@google.com>
-
- 09 Mar, 2010 1 commit
-
-
Jean-Baptiste Queru authored
Change-Id: Ied5f7eddd18adb38699c8a034a78ff9de4aab8de
-
- 03 Mar, 2010 1 commit
-
-
San Mehat authored
Add an un-encrypted superblock to the end of a secure container to help identify the crypto cipher used. This is required in order to provide some semblence of versioning, in case we have cause to change the crypto type on an update - say for example switching from software to hardware encryption, or from 128 -> a zillion bit keys. NOTE: This format is incompatible with previous secure containers. After this change they will no longer be mountable. Signed-off-by:
San Mehat <san@google.com>
-
- 02 Mar, 2010 2 commits
-
-
San Mehat authored
Signed-off-by:
San Mehat <san@google.com>
-
San Mehat authored
Signed-off-by:
San Mehat <san@google.com>
-
- 01 Mar, 2010 1 commit
-
-
San Mehat authored
Signed-off-by:
San Mehat <san@google.com>
-
- 24 Feb, 2010 5 commits
-
-
San Mehat authored
Signed-off-by:
San Mehat <san@google.com>
-
San Mehat authored
Signed-off-by:
San Mehat <san@google.com>
-
San Mehat authored
Signed-off-by:
San Mehat <san@google.com>
-
San Mehat authored
Signed-off-by:
San Mehat <san@google.com>
-
San Mehat authored
Signed-off-by:
San Mehat <san@google.com>
-
- 20 Feb, 2010 1 commit
-
-
San Mehat authored
In order to protect the '/android_secure' directory on VFAT removable media from being mucked with by 3rd party applications on the device, we hide the directory with a read-only, zero-sized tmpfs mounted on-top. A reference to the hidden directory is kept by a bind-mount which is mounted at a location which only root can access. Staging consists of: 1. Mount checked media at a secure location (/mnt/secure/staging) 2. Ensure /android_secure exists on the media, (creating if it doesnt) 3. Bind-mount /mnt/secure/staging/android_secure -> /mnt/secure/asec (where only root can access it) 4. Mount an RDONLY zero-sized tmpfs over /mnt/secure/staging/android_secure 5. Atomically move /mnt/secure/staging to the publicly accessable storage directory (/mnt/sdcard) Signed-off-by:
San Mehat <san@google.com>
-
- 18 Feb, 2010 4 commits
-
-
San Mehat authored
Signed-off-by:
San Mehat <san@google.com>
-
San Mehat authored
Signed-off-by:
San Mehat <san@google.com>
-
San Mehat authored
Signed-off-by:
San Mehat <san@google.com>
-
Kenny Root authored
Just in case someone tries to set up a series of links to trick us, do a quick sanity check on the total length of the strings we're about to concatenate. Change-Id: Iba9617008dbc1e93e1907393052caf1e52fbe312
-
- 17 Feb, 2010 1 commit
-
-
San Mehat authored
Signed-off-by:
San Mehat <san@google.com>
-
- 14 Feb, 2010 1 commit
-
-
San Mehat authored
Signed-off-by:
San Mehat <san@google.com>
-
- 11 Feb, 2010 2 commits
-
-
Jean-Baptiste Queru authored
Merge commit '4468682c' * commit '4468682c': new project, first commit
-
Jean-Baptiste Queru authored
-
- 08 Feb, 2010 1 commit
-
-
San Mehat authored
Signed-off-by:
San Mehat <san@google.com>
-
- 06 Feb, 2010 1 commit
-
-
San Mehat authored
Signed-off-by:
San Mehat <san@google.com>
-
- 04 Feb, 2010 1 commit
-
-
San Mehat authored
- share command was taking wrong arguments - shared command was returning two termination codes - Force FAT32 cluster size to 4k when formatting Signed-off-by:
San Mehat <san@google.com>
-
- 03 Feb, 2010 3 commits
-
-
San Mehat authored
Signed-off-by:
San Mehat <san@google.com>
-
San Mehat authored
Signed-off-by:
San Mehat <san@google.com>
-
San Mehat authored
Signed-off-by:
San Mehat <san@google.com>
-
- 02 Feb, 2010 1 commit
-
-
San Mehat authored
Signed-off-by:
San Mehat <san@google.com>
-
- 23 Jan, 2010 2 commits
-
-
San Mehat authored
Signed-off-by:
San Mehat <san@google.com>
-
San Mehat authored
Signed-off-by:
San Mehat <san@google.com>
-
- 22 Jan, 2010 1 commit
-
-
San Mehat authored
Signed-off-by:
San Mehat <san@google.com>
-
- 18 Jan, 2010 1 commit
-
-
San Mehat authored
Signed-off-by:
San Mehat <san@google.com>
-
- 15 Jan, 2010 1 commit
-
-
San Mehat authored
Signed-off-by:
San Mehat <san@google.com>
-
- 12 Jan, 2010 1 commit
-
-
San Mehat authored
Signed-off-by:
San Mehat <san@google.com>
-
- 11 Jan, 2010 4 commits
-
-
San Mehat authored
Signed-off-by:
San Mehat <san@google.com>
-
San Mehat authored
Signed-off-by:
San Mehat <san@google.com>
-
San Mehat authored
Signed-off-by:
San Mehat <san@google.com>
-
San Mehat authored
- Supports up to 4096 containers - Keys are now implemented - specifying a key of 'none' means no encryption. Otherwise, the key must be a string of 32 characters Signed-off-by:
San Mehat <san@google.com>
-