We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently applications (Notably keystone-demo, and sdk/tests) are required to keep track of their own expected pk hash for attestation.
Instead, the pk should keep track of its own expected hash, and make that available to applications to build against.
The text was updated successfully, but these errors were encountered:
See: https://github.com/keystone-enclave/keystone-demo/tree/master/include for examples of how the demo keeps track of hashes.
Sorry, something went wrong.
No branches or pull requests
Currently applications (Notably keystone-demo, and sdk/tests) are required to keep track of their own expected pk hash for attestation.
Instead, the pk should keep track of its own expected hash, and make that available to applications to build against.
The text was updated successfully, but these errors were encountered: