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

provision steps in section 4.2 #6

Open
PenglinYang opened this issue Aug 29, 2022 · 1 comment
Open

provision steps in section 4.2 #6

PenglinYang opened this issue Aug 29, 2022 · 1 comment

Comments

@PenglinYang
Copy link
Collaborator

3. Network user transfers UA and TA to confidential computing
resource via TAM. TAM then deploys these two applications in REE
and TEE respectively. (In SGX, UA must be deployed first, then
let the UA to deploy TA in SGX.)
4. TAM requests remote attestation to the TEEP Agent, TEEP Agent
then sends the evidence to TAM. The TAM works as the relying
party and forward the attestation result to network user

Clarify "deploy" and "load" in this case.
Is attestation result needs to be clarified in provision steps?

@PenglinYang
Copy link
Collaborator Author

  1. Network user transfers UA and TA to confidential computing device via TAM. TAM then deploys these two applications in REE and TEE respectively. (In SGX, UA must be deployed first, then let the UA to load TA in SGX.)
  2. TAM requests remote attestation to the TEEP Agent, TEEP Agent then sends the evidence to TAM. The TAM works as Verifier in RATs architecture.
  3. After verification,Network User works as Relying Party receives the attestation result. If positive, Network User establishes secure channel with TA, and deploys personalization data to the TA.

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

No branches or pull requests

1 participant