anonymous/android_bootable_recovery - Team Win Recovery Project (TWRP)

	Commit message (Collapse)	Author	Files	Lines
2019-09-01	Encryption: try wrapped key if the first time decryption fails	bigbiff bigbiff	1	-3/+3
	Change-Id: I108b7aeea41c6b85c851f40c1c4a7e25012e2463
2019-09-01	ext4crypt: support wrappedkey for FBE	Peter Cai	1	-2/+47
	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-01-17	Add metadata decrypt support for FBE	Ethan Yonker	1	-2/+3
	Change-Id: Ie0292f4ffea5993a4ae74fa04fc5c8252ca2cfcf
2018-08-31	Decrypt FBE on 9.0 (backwards compatible)	Ethan Yonker	1	-0/+861
	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