Skip to content

Refactor, crate updates, and printing measurements#1

Open
jakecorrenti wants to merge 3 commits intovirtee:mainfrom
jakecorrenti:add-measurements
Open

Refactor, crate updates, and printing measurements#1
jakecorrenti wants to merge 3 commits intovirtee:mainfrom
jakecorrenti:add-measurements

Conversation

@jakecorrenti
Copy link
Member

Refactor retrieving the kernel name to avoid manual string manipulation.

Update the time crate to a version including a CVE fix.

Print the measurements when building the EIF file is successful like the nitro-cli tool. This helps users use these measurements for attestation reference values.

Refactor how the kernel name is parsed to avoid manual string
manipulation.

Signed-off-by: Jake Correnti <jakecorrenti+github@proton.me>
`cargo audit` reported a vulnerability in the `time` crate. Update the
dependency to a version with the necessary fix.

Signed-off-by: Jake Correnti <jakecorrenti+github@proton.me>
Like the nitro-cli tool, print the measurements when the EIF file is
successfully built. This allows users to use those PCR values for
reference values during attestation.

Signed-off-by: Jake Correnti <jakecorrenti+github@proton.me>
Copy link
Member

@tylerfanelli tylerfanelli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One comment.


build.write_to(&mut output);
let measurements = build.write_to(&mut output);
println!("{:#?}", measurements);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would suggest the printing of measurements to be optional. Perhaps we should hide this behind a flag or something?

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants