Skip to content
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

Feature: Fetch OVMF and kernel command line arguments #194

Closed
danko-miladinovic opened this issue Aug 8, 2024 · 3 comments
Closed

Feature: Fetch OVMF and kernel command line arguments #194

danko-miladinovic opened this issue Aug 8, 2024 · 3 comments
Assignees
Labels
enhancement New feature or request help wanted Extra attention is needed question Further information is requested

Comments

@danko-miladinovic
Copy link
Contributor

Is your feature request related to a problem? Please describe.

This feature will enable the client (the member of the consortium) to fetch the missing information to calculate the measurement. The OVMF version, the kernel command line arguments, and the number of vcpus and vcpu-type.

Describe the feature you are requesting, as well as the possible use case(s) for it.

The idea is to enable the users to calculate the expected measurement that is needed during the aTLS verification and validation process.

Indicate the importance of this feature to you.

Must-have

Anything else?

No response

@danko-miladinovic danko-miladinovic added the enhancement New feature or request label Aug 8, 2024
@danko-miladinovic danko-miladinovic self-assigned this Aug 8, 2024
@dborovcanin
Copy link
Contributor

dborovcanin commented Sep 11, 2024

This potentially opens an attack vector because now we need to trust the manager-backend communication. We need to discuss this one @drasko @danko-miladinovic.

@dborovcanin dborovcanin added help wanted Extra attention is needed question Further information is requested labels Sep 11, 2024
@drasko
Copy link
Contributor

drasko commented Sep 11, 2024

@dborovcanin this is OK, because these measurements are signed with AMD firmware and SEV-SNP keys in the HW.

I would like to have more detailed explication how this approach maps to IETF RATS spec.

@dborovcanin
Copy link
Contributor

This is resolved in #245 by adding a measurement directly to the backend.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants