- 01 Sep, 2011 1 commit
-
-
Ken Sumrall authored
Add the force_and_revert option to the unmount command which will force the unmount, and revert a crypto mapping. This is used during factory reset so that when the internal sdcard volume is formatted, it formats the raw device, not the encrypted mapping. Change-Id: I36b6ff9bb54863b121de635472a303bf4a2334a9
-
- 11 Jul, 2011 1 commit
-
-
Ken Sumrall authored
Mounting was already not allowed, but also unshare before starting encryption, and don't allow sharing or formatting to be initiated during encrytion. Change-Id: Ida188d81f025739ba4dd90492b3e66088735991e
-
- 27 Jun, 2011 1 commit
-
-
Dianne Hackborn authored
Change-Id: Ife15628ed6e2493c9e85a2ade6d59a194fdddde5
-
- 18 Jun, 2011 1 commit
-
-
Mike Lockwood authored
Change-Id: I0e5fab1624e5ef5d2f55e2584d8adc1b6bab91b0 Signed-off-by:
Mike Lockwood <lockwood@android.com>
-
- 14 Jun, 2011 1 commit
-
-
Ken Sumrall authored
It is not a failure if the SD card is not mounted. Change-Id: If954f77c55ac124b9b7b39c89ffbafb4e5ea9e98
-
- 07 Jun, 2011 1 commit
-
-
Mike Lockwood authored
Change-Id: I8ac8900b3135f03b7717540b825ff6df76f31c0b Signed-off-by:
Mike Lockwood <lockwood@android.com>
-
- 02 Jun, 2011 1 commit
-
-
Ken Sumrall authored
Add support for keeping the keys in a separate file on another partition, for devices with no space reserved for a footer after the userdata filesystem. Add support for encrypting the volumes managed by vold, if they meet certain criteria, namely being marked as nonremovable and encryptable in vold.fstab. A bit of trickiness is required to keep vold happy. Change-Id: Idf0611f74b56c1026c45742ca82e0c26e58828fe
-
- 10 Dec, 2010 1 commit
-
-
Mike Lockwood authored
Change-Id: I9770ab880f379e2f7f6a93d3c84990edec60a116 Signed-off-by:
Mike Lockwood <lockwood@android.com>
-
- 28 Oct, 2010 1 commit
-
-
Mike Lockwood authored
Improves UI responsiveness when copying large amount of data to the device. BUG: 3131847 Change-Id: I4aa5ade7e2cd7e5110c8f0f7ee43bdc57577e11d Signed-off-by:
Mike Lockwood <lockwood@google.com>
-
- 01 Oct, 2010 1 commit
-
-
Kenny Root authored
ENOENT is more descriptive than the generic error that EINVAL gets turned into. Then we can actually treat it how we want on the other side. Change-Id: I9b4f3be6308e13f680eae368d2167ab9ee6aae5f
-
- 26 Sep, 2010 1 commit
-
-
Kenny Root authored
OBB and ASEC are tracked in the same active container list, but when it comes time to unmount everything, it was trying to unmount the OBBs according to ASEC rules. This led to the OBB not being unmounted and the volume unmount failing. Change-Id: I12c1d4d387b8022185d552b63edd61a50b9c0fc3
-
- 17 Sep, 2010 1 commit
-
-
Mike Lockwood authored
Only share a single partition via UMS if a specific partition is specified in vold.fstab (rather than "auto") Do not fail to reformat if MBR cannot be found. Change-Id: I544ca2ee325c308af656ab9f4732c788a964c156 Signed-off-by:
Mike Lockwood <lockwood@android.com>
-
- 02 Sep, 2010 1 commit
-
-
Kenny Root authored
This allows us to place shared libraries in these containers which may only be loaded if they are executable. Change-Id: I78fa9ab6d5c58ec8b98c40004da72aebc0aade2a
-
- 23 Jul, 2010 1 commit
-
-
Seth Forshee authored
Signed-off-by:
Seth Forshee <seth.forshee@garmin.com>
-
- 15 Jul, 2010 1 commit
-
-
Kenny Root authored
* Rename all functions dealing with OBB files to mention Obb * Add 'path' and 'list' functionality to OBB commands * Store hashed filename in loop's lo_crypt_name and keep lo_file_name for the real source filename. That way we can recover it later with an ioctl call. Change-Id: I29e468265988bfb931d981532d86d7be7b3adfc8
-
- 07 Jul, 2010 1 commit
-
-
Kenny Root authored
Allow the mounting of OBB filesystem images if they're encrypted with twofish and in FAT filesystem format. Change-Id: I54804e598f46b1f3a784ffe517ebd9d7626de7aa
-
- 28 Jun, 2010 1 commit
-
-
Mike Lockwood authored
The usb_mass_storage switch no longer exists in our 2.6.35 kernel. Instead we will consider mass storage to be available if both USB is connected and the USB mass storage function is enable. Change-Id: I730d1b3cb3cac664fc2abcdc36cd39856a08404a Signed-off-by:
Mike Lockwood <lockwood@android.com>
-
- 21 Jun, 2010 1 commit
-
-
Kenny Root authored
Hash was printed using snprintf(), but we can just write yet another hex conversion utility! Change-Id: I04f1992deaf5bf1b3e2751c8f07072f8ed6660e9
-
- 15 Apr, 2010 1 commit
-
-
San Mehat authored
Fixes bug: http://b/issue?id=2567572 Note: The framework will still likely restart since the system_server is holding references to assets on the card which are mmaped, but at least now storage will be available when a new card is re-inserted. Change-Id: I4e195c0c666426b93da47198fa826a6f58d855a9 Signed-off-by:
San Mehat <san@google.com>
-
- 25 Mar, 2010 1 commit
-
-
San Mehat authored
Change-Id: I48ee8bd90b47f5845f069cdf4d1b8ba6ecdb1b39 Signed-off-by:
San Mehat <san@google.com>
-
- 23 Mar, 2010 1 commit
-
-
San Mehat authored
Change-Id: Icbe3de7c28505f7496c8f8edea126c7b616de475 Signed-off-by:
San Mehat <san@google.com>
-
- 17 Mar, 2010 1 commit
-
-
San Mehat authored
Change-Id: If025e7ee10a79ff089920a6d0c1a52358b2d2c22 Signed-off-by:
San Mehat <san@google.com>
-
- 15 Mar, 2010 2 commits
-
-
Kenny Root authored
Change-Id: I9b84370fa9a98464c211ebe8983be8dbe9dd7ccd
-
San Mehat authored
Change-Id: Iaeb5d3334ec22ed31da9734bb8d7cd17e6a40eaf Signed-off-by:
San Mehat <san@google.com>
-
- 14 Mar, 2010 1 commit
-
-
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>
-
- 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>
-
- 01 Mar, 2010 1 commit
-
-
San Mehat authored
Signed-off-by:
San Mehat <san@google.com>
-
- 24 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>
-
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 2 commits
-
-
San Mehat authored
Signed-off-by:
San Mehat <san@google.com>
-
San Mehat authored
Signed-off-by:
San Mehat <san@google.com>
-
- 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>
-
- 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 1 commit
-
-
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 1 commit
-
-
San Mehat authored
Signed-off-by:
San Mehat <san@google.com>
-