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

Labels

Member

rvolosatovs commented Dec 6, 2022 •

edited

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"

The text was updated successfully, but these errors were encountered:

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 added the attestation label

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