Skip to content

Conversation

@alicefr
Copy link
Contributor

@alicefr alicefr commented Oct 29, 2025

No description provided.

Signed-off-by: Alice Frosi <afrosi@redhat.com>
Copy link
Contributor

Choose a reason for hiding this comment

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

  • Remote attestation is initiated by Ignition but performed by the attester, isn't it?
  • By "attestation token", you mean one à la https://github.com/confidential-containers/trustee/blob/main/attestation-service/docs/grpc-as.md#quick-start? Is it going to verify against Trustee (that should be in the diagram) or something else (what/how?)?
  • Interaction between Ignition and Trustee attester for the disk key phase maybe?
  • I know the diagram in the booting design document is mighty large as is, but I'm not sure I'd split it up this way where the reader must basically merge this diagram into a bigger slightly inaccurate diagram in their head to understand the flow. It would be easier if they could append two diagrams, e.g. if you split by phase? Then you could drop the registration service in the second phase.

- Uses generic reference values for the image (no UUID)
- Proves the platform is running in a confidential computing environment

2. **Attestation Token Received**: Trustee Attester validates the attestation and returns an attestation token
Copy link

Choose a reason for hiding this comment

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

Trustee validates ... (remove Attester)

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.

3 participants