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

Seed for TAM protocol #31

Closed
nicopal opened this issue Oct 24, 2018 · 4 comments
Closed

Seed for TAM protocol #31

nicopal opened this issue Oct 24, 2018 · 4 comments
Assignees
Labels
ready to close Ready for WG chairs to verify and close

Comments

@nicopal
Copy link

nicopal commented Oct 24, 2018

Section 7.1 Attestation Hierarchy mentions that "seed required for TAM protocol operation must be built into the device at manufacture".

This is technically correct, but considering that the architecture assumes the presence of multiple TEEs on the device, it could be rephrased as "seed required for TAM protocol operation must be built into the TEE at manufacture".

@hannestschofenig
Copy link
Collaborator

I looked into the text and I wonder whether we really need to talk about the seed in the architecture document. To me it sounds like providing a bit too much details about the OTrP protocol in the architecture draft. Hence, I am proposing to remove the seed concept from the architecture document to resolve this comment.

@hannestschofenig
Copy link
Collaborator

Section 7.1 should briefly talk about what attestation in the context of TEEP is and what we are trying to accomplish.

@hannestschofenig
Copy link
Collaborator

Related to issue #17

@mingpeiwk
Copy link
Collaborator

This will be addressed in attestation discussion update in the draft. Seeding of attestation keys will be discussed where seeding at manufacture becomes one of the ways, not the only way. The overall trust of attestation claims will have a list of assumptions for an attestation key to be trusted.

dthaler added a commit that referenced this issue Nov 26, 2019
Align picture with diagrams used in the TEEP WG at IETF 105

THis addresses issues #17, #31, and the part of #70 that talks about
digital signature formats.  Per discussion at IETF 106, the direction is
that the architecture document should explain the relationship between
TEEP and attestation, and leave protocol details to the TEEP protocol
spec. It should NOT discuss attestation details, including anything
about signing with any attestation key, seeding of attestation keys,
or using specific crypto algorithms for attestation.

Signed-off-by: Dave Thaler <dthaler@microsoft.com>
@dthaler dthaler assigned dthaler and unassigned dmwheel1 Nov 26, 2019
@dthaler dthaler added the have proposed text Ready for other editors to review and merge if ok label Nov 26, 2019
@dthaler dthaler added ready to close Ready for WG chairs to verify and close and removed have proposed text Ready for other editors to review and merge if ok labels Dec 7, 2019
@dthaler dthaler assigned ncamwing and unassigned dthaler Dec 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready to close Ready for WG chairs to verify and close
Projects
None yet
Development

No branches or pull requests

7 participants