android_bootable_recovery

Author	SHA1	Message	Date
Noah Jacobson	0b25b1d79b	Add support for multi-user decryption * Add CLI support using the command "twrp decrypt <PASSWORD> [USER ID]" * Add GUI support using the menu Advanced --> Decrypt User Change-Id: Id2681bc2b1012a0571417f7a6e0b980b1b25c61c (cherry picked from commit 5a79f67a1b1bd1bcadeca0a4896a871646652534)	2020-05-20 19:11:15 -04:00
bigbiff bigbiff	0be03b3217	Encryption: try wrapped key if the first time decryption fails Change-Id: I108b7aeea41c6b85c851f40c1c4a7e25012e2463	2019-09-01 13:38:44 -04:00
Peter Cai	90edd2e867	ext4crypt: support wrappedkey for FBE Qualcomm devices use a special `wrappedkey` mode for FBE. This is ported from CAF https://source.codeaurora.org/quic/la/platform/system/vold/commit/?h=LA.UM.7.8.r4-01000-SDM710.0&id=9229262d893a8592f7bc1b4e8a8dab7aad8df68c, originally by folks at Mokee for vold https://mokeedev.review/c/MoKee/android_system_vold/+/34102. This patch ports the above changes to `ext4crypt`, which we can use in recovery. Note that since we do not have `fs_mgr` in the recovery, we cannot read the `wrappedkey` flag from fstab. Instead, similar to `fbe.contents`, we use a special property `fbe.data.wrappedkey` to indicate support for wrappedkey mode. Devices that need to use this should set this property to `true` to activate corresponding code. Change-Id: I79c2855d577156670b45c10c7c7b1fcd9fece8d9	2019-09-01 19:33:30 +02:00
Ethan Yonker	933828251d	Add metadata decrypt support for FBE Change-Id: Ie0292f4ffea5993a4ae74fa04fc5c8252ca2cfcf	2019-01-17 14:14:59 -06:00
Ethan Yonker	e9afc3de0f	Decrypt FBE on 9.0 (backwards compatible) Building in 9.0 may require you to add a flag to your twrp fstab with the fileencryption details like: fileencryption=ice:aes-256-heh Verify this against your device's stock fstab of course. Change-Id: If9286f5d5787280814daca9fbc8f5191ff26a839	2018-08-31 10:37:08 -05:00

5 Commits