-
Notifications
You must be signed in to change notification settings - Fork 111
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
Generate empty attestation config #4808
Generate empty attestation config #4808
Conversation
… by the restricted kernel SDK
… evidence as OakRestrictedKernel
@@ -23,10 +23,15 @@ | |||
|
|||
extern crate alloc; | |||
|
|||
use alloc::vec; | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: extra newline? Or do you treat alloc differently?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
automatically formatted by rustfmt. its ways are mysterious
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The new format used by rustfmt groups core/alloc/std together, all third-party ctates together and all local crate::
imports together.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
@@ -23,10 +23,15 @@ | |||
|
|||
extern crate alloc; | |||
|
|||
use alloc::vec; | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The new format used by rustfmt groups core/alloc/std together, all third-party ctates together and all local crate::
imports together.
This field is currently not populated by the restricted kernel, as there is no application config. However, the verification library expects it.
Depending on preference, this field should either be populated with an empty value (this PR) or removed #4807.
Those PRs are mutually exclusive. But one should be merged, for restricted kernel evidence to be parsed in the verification library.