anonymous/android_bootable_recovery - Team Win Recovery Project (TWRP)

	Commit message (Collapse)	Author	Age	Files	Lines
*	Merge \"Clean up verifier testcases.\"	Tao Bao	2016-08-01	20	-0/+4
\|\ \| \| \| \| \| \| \| \| \| \|	am: e91aef0ee9 Change-Id: Ia130dc2a7f62ecf1ad40ec03d88a331a31800efa
\| *	Clean up verifier testcases.	Tao Bao	2016-08-01	20	-0/+4
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	A Certificate is a pair of an RSAPublicKey and a particular hash. So v1 and v3 differ in the hash algorithm (SHA-1 vs SHA-256), similarly for v2 and v4. In verifier testcases, we used to load v1/v2 keys with an explicit argument of "sha256" to test the v3/v4 keys. This CL switches to loading v3/v4 keys directly and lets load_keys() to handle that, which is the actual flow we use in practice. Also remove the "fallback to v1 key" in the testcases, which is not the actual behavior. Bug: 30415901 Test: Run the verifier_test component test on device. Change-Id: I3a2baa64826f1b6c4c367a560090df384c4521bb
* \|	resolve merge conflicts of 2bf95ac to nyc-dev-plus-aosp	Elliott Hughes	2016-04-13	3	-0/+3
\|\\| \| \| \| \| \| \|	Change-Id: Iaf232fbe65879bad6e19c7a9600aa6303a491a67
\| *	Convert recovery to use BoringSSL instead of mincrypt.	Mattias Nissler	2016-04-06	3	-0/+3
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	This changes the verification code in bootable/recovery to use BoringSSL instead of mincrypt. Change-Id: I37b37d84b22e81c32ac180cd1240c02150ddf3a7
* \|	Port applypatch.sh tests to recovery_component_tests	Jed Estep	2016-03-12	3	-0/+0
\|/ \| \| \| \|	Bug: 27135282 Change-Id: If53682b591397ddfdb84860a3779b612904d4489
*	Refactor existing tests to use gtest	Jed Estep	2016-02-04	19	-0/+114
	Bug: 26962907 Change-Id: I5f80636af1740badeff7d08193f08e23f4e4fee1