You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chip-tool only knows of the TestAttestationTrustStore which only contains a well-known insecure PAA key. We need to be able to scale to having chip-tool capable of commissioning devices with real PAAs.
Proposed Solution
Make chip-tool configurable to receive a path to a location containing a mirror of the DCL's official PAA trust store.
The text was updated successfully, but these errors were encountered:
- This PR is on the way to resolving project-chip#15209.
- This PR does the following:
- Splits DefaultDeviceAttesationVerifier from the main src/credentials target
since it is an optional component that can be overridden by different
commissioners
- Adds the beginning of plumbing to properly select the Trust Store for
the DefaultDeviceAttestationVerifier.
- Moved DefaultDeviceAttestatationVerifier from credentials/examples to
credentials/attestation_verifier
Missing, to come in the follow-up:
- The implementation of a new file-based PAA trust store configured with
the path passed in the plumbing added here.
Testing done: unit tests and cert tests still pass. Commissioning still works
* Separate DefaultDeviceAttestationVerifier from credentials
- This PR is on the way to resolving #15209.
- This PR does the following:
- Splits DefaultDeviceAttesationVerifier from the main src/credentials target
since it is an optional component that can be overridden by different
commissioners
- Adds the beginning of plumbing to properly select the Trust Store for
the DefaultDeviceAttestationVerifier.
- Moved DefaultDeviceAttestatationVerifier from credentials/examples to
credentials/attestation_verifier
Missing, to come in the follow-up:
- The implementation of a new file-based PAA trust store configured with
the path passed in the plumbing added here.
Testing done: unit tests and cert tests still pass. Commissioning still works
* Restyled by clang-format
* Restyled by gn
* Fix ESP32 Qemu test
* Fix CHIPCommandBridge
Co-authored-by: Restyled.io <[email protected]>
Problem
chip-tool only knows of the
TestAttestationTrustStore
which only contains a well-known insecure PAA key. We need to be able to scale to having chip-tool capable of commissioning devices with real PAAs.Proposed Solution
The text was updated successfully, but these errors were encountered: