Skip to content

Conversation

@arianvp
Copy link

@arianvp arianvp commented Nov 14, 2025

No description provided.

## UKI Components
UKIs consist of the following resources:

<!-- NOTE: these components are in canonical for predictable PCR measurements. Please add any new components at the bottom of the list and NEVER reorder anything in this list. -->
Copy link
Member

Choose a reason for hiding this comment

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

Linebreak between the sentences please.

Why draft?

@arianvp arianvp marked this pull request as ready for review November 14, 2025 15:22
Co-authored-by: Jörg Behrmann <behrmann@physik.fu-berlin.de>

<!--
NOTE: these components are in canonical order for predictable PCR measurements.
Please add any new components at the bottom of the list and NEVER reorder anything in this list.
Copy link
Member

Choose a reason for hiding this comment

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

Actually I think pcrsig and pcrpkey are the exception to this? IE, new things should be added before .pcrsig, but these two are never used for measurements

Copy link
Author

Choose a reason for hiding this comment

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

This is not true. .pcrpkey is measured.

Copy link
Member

Choose a reason for hiding this comment

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

Before the pub key one then? I haven't checked

@poettering
Copy link
Collaborator

I don't think should be a comment. If we define a canonical order, then we should say so in the spec, and not in a comment in the spec. Hence please reword this, and make this regular text

@arianvp
Copy link
Author

arianvp commented Nov 27, 2025

That was my original plan but @bluca said I should do a comment instead. Can y'all come to consensus before I move forward? I don't want to ping-pong back and forth

@bluca
Copy link
Member

bluca commented Nov 27, 2025

It's fine to say it in the spec too (I'd also keep the comment immediately above so that it's harder to accidentally miss)

@poettering
Copy link
Collaborator

Any chance you can add a brief comment to the visible part of the spec as suggested? seems good to go otherwise

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

Development

Successfully merging this pull request may close these issues.

5 participants