Skip to content
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

[TC-DA-1.5, 1.6]chip-tool- NOCSR Procedure Validation-Support Required #14404

Closed
2 tasks done
sumaky opened this issue Jan 27, 2022 · 7 comments
Closed
2 tasks done

[TC-DA-1.5, 1.6]chip-tool- NOCSR Procedure Validation-Support Required #14404

sumaky opened this issue Jan 27, 2022 · 7 comments

Comments

@sumaky
Copy link
Contributor

sumaky commented Jan 27, 2022

Problem

  • Support Required to verify the following (DUT as Commissionee):
  1. DUT generates the NOCSR Information using CSRResponse Command
  2. DUT generated NOCSR Information includes a signature using the Device Attestation Private Key
  3. CSR SHALL follow the encoding and rules from PKCS Update cxx_rules #10
  4. DUT generated that Node Operational Key Pair is unique
  5. DUT rejects invalid CSRNonce sent by TH1
  6. csr field is DER-encoded octet string
  7. csr follows the encoding and rules from PKCS Update cxx_rules #10
  8. CSRNonce field is OCTET string of length 32
  9. CSRNonce value should match the value CSR Nonce field in the corresponding CSRRequest Command
  10. Verify that NOCSRElement size should not be greater than RESP_MAX (900 bytes)
  • Support required to inject the following error in NOCSR Information-CSRRequest Command to test DUT as Commissioner
  1. CSRNonce is OCTET string of length> 32
  2. CSRNonce value does not match the value CSR Nonce field in the corresponding CSRRequest Command
  3. NOCSRElement size is greater than RESP_MAX
  4. Invalid NOCSR with an existing key pair

Test Plan Link
https://github.com/CHIP-Specifications/chip-test-plans/blob/master/src/deviceattestation.adoc

@woody-apple
Copy link
Contributor

Cert Blocker Review: Assigning to @vivien-apple

@franck-apple
Copy link

First part (first checkbox) should be fixed by Vivien's PR #18893.
Second part to come.

@vivien-apple
Copy link
Contributor

Most of second part is in #19461

It is just missing "Invalid NOCSR with an existing key pair" since I'm not sure of what it implies. @emargolis can you help me understand this part ?

@vivien-apple
Copy link
Contributor

Most of second part is in #19461

It is just missing "Invalid NOCSR with an existing key pair" since I'm not sure of what it implies. @emargolis can you help me understand this part ?

I checked with @tcarmelveilleux what needs to be done. I will do it in a separate PR as it is a bit more involved than the previous cases.

@vivien-apple
Copy link
Contributor

Most of second part is in #19461
It is just missing "Invalid NOCSR with an existing key pair" since I'm not sure of what it implies. @emargolis can you help me understand this part ?

I checked with @tcarmelveilleux what needs to be done. I will do it in a separate PR as it is a bit more involved than the previous cases.

The last part is in #19528.

@krypton36
Copy link
Contributor

krypton36 commented Jun 15, 2022

Spoke to @vivien-apple offline and the steps to test "Invalid NOCSR with an existing key pair" CSRResponse is as follows after #19528 is merged:

1. Start all-clusters-app with cert_error_csr_existing_keypair
2. Pair all-clusters-app using chip-tool (KeyPair Generated)
3. Open a commissioning window using your preferred method
4. Pair all-clusters-app using chip-tool with a "different fabric" (Should Fail using existing KeyPair)

@vivien-apple
Copy link
Contributor

The dependencies has been merged. Closing this one. Please open specific issues if anything pops up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants