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.

Sign up for GitHub

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

Jump to bottom

Attestation config format #138

Open
rvolosatovs opened this issue Dec 6, 2022 · 1 comment
Open

Attestation config format #138

rvolosatovs opened this issue Dec 6, 2022 · 1 comment
Labels
attestation Issues related to attestation

Comments

@rvolosatovs
Copy link
Member

rvolosatovs commented Dec 6, 2022 •
edited
Loading

In #107 a multitude of X and X_blacklist fields are added and not all of these are consistent.

How about we have [deny] and [allow] sections instead?

E.g.:

[sgx.allow]
hash = "DEADBEEF"
signer = "BEEFDEAD"

[sgx.deny]
signer = "C0FFEE"
@rjzak
Copy link
Member

rjzak commented Dec 6, 2022

  • How would this look in code? Is this a simple Serde rename?
  • What about other items in SGX and SNP? Would it be like below, and is that too many [sections]?:
[sgx.allow]
hash = "DEADBEEF"
signer = "BEEFDEAD"

[sgx.deny]
signer = "C0FFEE"

[sgx]
features = ["Debug", "ProvisioningKey", "EInitKey", "KSS"]
enclave_security_version = 0
enclave_product_id = 0

@rjzak rjzak added the attestation Issues related to attestation label Dec 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
attestation Issues related to attestation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rjzak @rvolosatovs