-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for generation and verification of CSR attestation signature #11908
Comments
- Add actual attestation signature to NOCSR elements - Add ability to generate the vendor-reserved elements - Move TLV struct size estimator to TLV library - Add more logs to NOC cluster - Refactor NOC cluster to use common signature logic for CSRResponse and AttestationResponse - Add a good limit on CSR size to reduce memory (a real spec-compliant CSR is 220-230 bytes Fixes project-chip#8729 Issue project-chip#11908 Testing done: added unit tests and ran test_suites.sh integration tests
* Use spec-compliant NOCSR elements - Add actual attestation signature to NOCSR elements - Add ability to generate the vendor-reserved elements - Move TLV struct size estimator to TLV library - Add more logs to NOC cluster - Refactor NOC cluster to use common signature logic for CSRResponse and AttestationResponse - Add a good limit on CSR size to reduce memory (a real spec-compliant CSR is 220-230 bytes Fixes #8729 Issue #11908 Testing done: added unit tests and ran test_suites.sh integration tests * Restyled by clang-format * Fix signedness warning * Fix signedness issue in perfect forwarding * Address review comments * Restyled by clang-format * Fixed bug when vendor reserved data missing * Restyled by clang-format Co-authored-by: Restyled.io <[email protected]>
@tcarmelveilleux Please review the merged PRs and confirm if this issue is addressed |
@tcarmelveilleux is there any remaining task for this ticket? |
AutoCommissioner should at least check attestation signature on receipt of CSRResponse. This is the MVP for 1.0 |
Tennessee, can you just clarify what you want here? Do you want the auto commissioner to call VerifyNodeOperationalCSRInformation? Or do you want it to verify the generated cert chain? We verify the CSR information right before we generate the NOC chain. I suppose we can pull this out into a separate step so folks that opt to replace the auto commissioner can call that as a separate step. |
From offline discussion - twofold answer for this issue.
|
Problem
Spec requires an attestation signature on the CSR. This attestation signature must then be validated by commissioner logic. This is currently omitted in the SDK.
Proposed Solution
The text was updated successfully, but these errors were encountered: