anonymous/android_bootable_recovery - Team Win Recovery Project (TWRP)

	Commit message (Collapse)	Author	Files	Lines
2016-10-04	edify: Move State.script and State.errmsg to std::string.	Tao Bao	1	-6/+1
	This way we kill a few strdup() and free() calls. Test: 1. recovery_component_test still passes; 2. Applying an update with the new updater works; 3. The error code in a script with abort("E310: xyz") is recorded into last_install correctly. Change-Id: Ibda4da5937346e058a0d7cc81764d6f02920010a
2016-10-04	edify: Move the testcases to gtest.	Tao Bao	1	-0/+156
	Now they live in tests/component/edify_test.cpp. Also rename edify/main.cpp to edify/edify_parser.cpp. It becomes a host-side debugging tool that validates the input edify script. However, it supports edify builtin functions only and doesn't recognize the ones defined via updater. Test: recovery_component_test passes on device. Change-Id: Ib94a787bf15098a9cc078d256b6a6dc96ff12b2e
2016-08-26	Fix clang-tidy warnings in bootable/recovery.	Chih-Hung Hsieh	1	-1/+1
	* Use const reference type for read-only parameters. Bug: 30407689 * Use faster overloaded string find function. Bug: 30411878 * Add parentheses around macro parameters. Bug: 28705665 Test: build with WITH_TIDY=1 Change-Id: I4e8e5748bfa4ae89871f1fb5fa4624d372530d75
2016-08-01	Clean up verifier testcases.	Tao Bao	1	-41/+26
	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
2016-04-29	Add ability to show "installing security update"	Tianjie Xu	1	-0/+1
	Add a new command "--security" to boot commands. If this command is observed as part of BCB, choose a different background text picture for installing stage in recovery UI. As a result, users will see "installing security update" instead of "installing system update" when applying a security update package. Bug: 27837319 Change-Id: I2e2253a124993ecc24804fa1ee0b918ac96837c5
2016-04-14	Use BoringSSL instead of mincrypt to speed up package verification.	Elliott Hughes	1	-108/+23
	This changes the verification code in bootable/recovery to use BoringSSL instead of mincrypt. Cherry-pick of 452df6d99c81c4eeee3d2c7b2171901e8b7bc54a, with merge conflict resolution, extra logging in verifier.cpp, and an increase in the hash chunk size from 4KiB to 1MiB. Bug: http://b/28135231 Change-Id: I1ed7efd52223dd6f6a4629cad187cbc383d5aa84
2016-04-06	Convert recovery to use BoringSSL instead of mincrypt.	Mattias Nissler	1	-108/+23
	This changes the verification code in bootable/recovery to use BoringSSL instead of mincrypt. Change-Id: I37b37d84b22e81c32ac180cd1240c02150ddf3a7
2016-03-12	Port applypatch.sh tests to recovery_component_tests	Jed Estep	2	-6/+393
	Bug: 27135282 Change-Id: If53682b591397ddfdb84860a3779b612904d4489
2016-02-22	Fix verifier test base testdata directory after merge conflict	Jed Estep	1	-1/+1
	Change-Id: I7ffba0be5a6befc875ce59b51a008c1892e7d34b
2016-02-05	Change on-device directory for recovery test data	Jed Estep	1	-1/+1
	Test data needs to go outside the gtest module. Change-Id: Ic444ca838cbafa651ec97ff8730129da84fafc09
2016-02-05	verifier_test: Suppress the unused parameter warnings.	Tao Bao	1	-8/+9
	Change-Id: I51fec30114c0a31efc9c2ac8472654baf8bb3e84
2016-02-04	Refactor existing tests to use gtest	Jed Estep	1	-0/+267
	Bug: 26962907 Change-Id: I5f80636af1740badeff7d08193f08e23f4e4fee1