Use of Evidence generating key material for AE identification #399
+6
−5
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
henkbirkholz
requested review from
thomas-fossati,
yogeshbdeshpande and
nedmsmith
as code owners
draft-ietf-rats-corim.md
Outdated
|
|
||
| The integrity of public and private key material and the secrecy of private key material must be ensured at all times. | ||
| This includes key material carried in attestation key triples and key material used to verify the authority of triples (such as public keys that identify trusted supply chain actors). | ||
| For more detailed information on protecting Trust Anchors, refer to {{Section 12.4 of -rats-arch}}. | ||
| As it is possible to use the public part of an asymmetric key pair for Evidence generation to be used to identify an Attesting Environment, this method of potentially identifying unique instances of Attesting Environments (and profiling their respective owners) can come with privacy considerations that have to be carefully weighed. |
There was a problem hiding this comment.
The text here is not clear to me?
Are we saying:
- Asymmetric Key Pair used to sign the Evidence OR
- Public Part of Asymmetric Key pair is part of Evidence Claim used to identify the Attesting Env?
There was a problem hiding this comment.
Public keys are PII unless they are for group signing (where the size of the group is privacy preserving).
There was a problem hiding this comment.
Are we saying:
Asymmetric Key Pair used to sign the Evidence OR Public Part of Asymmetric Key pair is part of Evidence Claim used to identify the Attesting Env?
Yes. That happens and is a PII issue.
There was a problem hiding this comment.
Public keys are PII unless they are for group signing (where the size of the group is privacy preserving).
Yes. Is the DAA scenario relevant here?
nedmsmith
reviewed
Feb 24, 2025
draft-ietf-rats-corim.md
Outdated
|
|
||
| The integrity of public and private key material and the secrecy of private key material must be ensured at all times. | ||
| This includes key material carried in attestation key triples and key material used to verify the authority of triples (such as public keys that identify trusted supply chain actors). | ||
| For more detailed information on protecting Trust Anchors, refer to {{Section 12.4 of -rats-arch}}. | ||
| As it is possible to use the public part of an asymmetric key pair for Evidence generation to be used to identify an Attesting Environment, this method of potentially identifying unique instances of Attesting Environments (and profiling their respective owners) can come with privacy considerations that have to be carefully weighed. |
There was a problem hiding this comment.
Public keys are PII unless they are for group signing (where the size of the group is privacy preserving).
Co-authored-by: Thomas Fossati <[email protected]>
yes Co-authored-by: Thomas Fossati <[email protected]>
okay Co-authored-by: Ned Smith <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes #156