summaryrefslogtreecommitdiff
path: root/security/keymint/aidl/vts/functional/DeviceUniqueAttestationTest.cpp
Commit message (Collapse)AuthorAgeFilesLines
* KeyMint VTS: extra unique ID testDavid Drysdale2021-11-101-16/+24
| | | | | | | | | Test that specifying RESET_SINCE_ID_ROTATION results in a different unique ID value. Test: VtsAidlKeyMintTargetTest Bug: 202487002 Change-Id: I2aed96514bf9e4802f0ef756f880cac79fa09554
* KeyMint: Fix device-unique attestation chain specificationEran Messeri2021-07-091-4/+9
| | | | | | | | | | | | | | | | | | | | | | Fix the device-unique attestation chain specification: The chain should have two or three certificates. In case of two certificates, the device-unique key should be used for the self-signed root. In case of three certificates, the device-unique key should be certified by another key (ideally shared by all StrongBox instances from the same manufacturer, to ease validation). Adjust the device-unique attestation tests to accept two or three certificates in the chain. Additionally, the current StrongBox KeyMint implementation can not yet generate fully-valid chains (with matching subjects and issuers), so relax that check. Bug: 191361618 Test: m VtsAidlKeyMintTargetTest Merged-In: I6e6bca33ebb4af67cac8e41a39e9c305d0f1345f Change-Id: Iebefafe72148c919d10308eff7a19fc1bc40c619
* KeyMint VTS: improve attestation testsDavid Drysdale2021-06-171-27/+159
| | | | | | | | | | | | | | Check that the various ATTESTATION_ID_* tags are included if they have the correct value, and that keygen fails if they have an invalid value. Also update attestation tags to include vendor/boot patchlevel if they're available. (They always should be, but fixing that is a separate task.) Bug: 190757200 Test: VtsAidlKeyMintTargetTest Change-Id: Ibaed7364c6d08c0982e2a9fb6cb864ae42cf39fe
* Improve unique attestation docs & testsEran Messeri2021-06-161-1/+4
| | | | | | | | | | | | | | | Improve the documentation and tests related to device-unique attestation on StrongBox KeyMint devices: * Test that the chain produced is exactly of length 2. * Document how the chain needs to be structured. * Explain the trust properties of the key used for the self-signed root. Test: atest VtsAidlKeyMintTargetTest Bug: 187803288 Ignore-AOSP-First: Already merged in AOSP Merged-In: I09bb16d6938b567c114485d2df00bde9d3e1ccf9 Change-Id: Ib7efdd428ce5a2e14c281077e3a77048c9721702
* KeyMint: improve HAL spec and testsDavid Drysdale2021-05-211-2/+2
| | | | | | | | | | | | | - clarify & test BIGNUM spec - allow alternative return codes when requesting device unique attestation - use specific error for early boot import failure - test more early boot key scenarios (in post-early-boot mode) Bug: 188672564 Test: VtsAidlKeyMintTargetTest Merged-In: I70a342084a29144aef1ed0ff80fec02cc06ffbc0 Change-Id: I70a342084a29144aef1ed0ff80fec02cc06ffbc0
* Merge "vts: Correct the parameters on strongbox"Tommy Chiu2021-05-051-2/+0
|\
| * vts: Correct the parameters on strongboxTommy Chiu2021-05-041-2/+0
| | | | | | | | | | | | | | | | | | | | | | If GenerateKey() with user-provide key_blob, it needs to be specified in the following begin() operations as well. Update the test case just to take key_blob from private member instead of creating a local one. Note: - Remove redudent TAG_NO_AUTH_REQUIRED in DeviceUniqueAttestationTest Change-Id: I81860294e1e7e01a57e66e08e75507a8292ec0c3
* | Update DeviceUniqueAttestationTest to match specShawn Willden2021-05-031-2/+2
|/ | | | | Test: VtsAidlKeyMintTargetTest Change-Id: Ic8949e223eb7ba2445d4738dcd9b31a1d244bb46
* Implement device unique attestation vts tests for keymint.Selene Huang2021-04-211-0/+193
Test: atest VtsAidlKeyMintTargetTest Change-Id: If271c915d33cece035ab67b9149ae4ba762648b4
generated by cgit v1.2.3 (git 2.25.1) at 2025-12-21 04:50:42 +0000