Fix: CRN API did not expose CPU features for trusted computing #622
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Trusted computing requires CPU features such as
sev
,sev_es
andsev_snp
.This adds the field
properties.cpu.features
/about/usage/system
as a list of CPU features.Currently, only SEV related features are present, but more can be added, for example
avx2
,fma
andf16c
. Adding them will require ensuring that they are actually active and not just present on the CPU via/proc/cpuinfo
.This work is based on a proposal to add the relevant field on aleph-message: aleph-im/aleph-message#100
Example JSON output: