summaryrefslogtreecommitdiffstats
path: root/tests/testdata/testkey_ecdsa.pk8 (unfollow)
Commit message (Collapse)AuthorFilesLines
2016-08-01Clean up verifier testcases.Tao Bao1-0/+0
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-02-04Refactor existing tests to use gtestJed Estep1-0/+0
Bug: 26962907 Change-Id: I5f80636af1740badeff7d08193f08e23f4e4fee1
2013-10-10Add support for ECDSA signaturesKenny Root1-0/+0
This adds support for key version 5 which is an EC key using the NIST P-256 curve parameters. OTAs may be signed with these keys using the ECDSA signature algorithm with SHA-256. Change-Id: Id88672a3deb70681c78d5ea0d739e10f839e4567