Skip to content

Conversation

@vathpela
Copy link
Member

@hughsie asked me to also make it observable at runtime whether the shim binary that was used to boot was set as NX_COMPAT or not.

This adds that into the HSIStatus data as "shim-has-nx-compat-set".

@vathpela vathpela marked this pull request as ready for review February 24, 2025 22:29
@vathpela vathpela force-pushed the show-nx-compat-in-hsi branch from e369da2 to 9af5fcf Compare February 24, 2025 22:33
@hughsie
Copy link

hughsie commented Feb 25, 2025

Many thanks @vathpela -- this makes the output much more useful.

@vathpela vathpela force-pushed the show-nx-compat-in-hsi branch from ea61e77 to 1991560 Compare February 25, 2025 15:48
Signed-off-by: Peter Jones <pjones@redhat.com>
This changes all the HSI bitfield operations to print a string showing
the change instead of just hex values.

Signed-off-by: Peter Jones <pjones@redhat.com>
When we're parsing the PE header of shim itself from the Loaded Image
object, the signatures aren't present, but the Certificate Table entry
in the Data Directory has not been cleared, so it'll fail verification.

We know when we're doing that, so this patch makes that test optional.

Signed-off-by: Peter Jones <pjones@redhat.com>
hughsie asked me to also make it observable at runtime whether the shim
binary that was used to boot was set as NX_COMPAT or not.

This adds that into the HSIStatus data as "shim-has-nx-compat-set".

Signed-off-by: Peter Jones <pjones@redhat.com>
Signed-off-by: Peter Jones <pjones@redhat.com>
Signed-off-by: Peter Jones <pjones@redhat.com>
@vathpela vathpela force-pushed the show-nx-compat-in-hsi branch from 1991560 to 6534fe9 Compare February 25, 2025 16:52
@vathpela vathpela merged commit 5007d83 into rhboot:main Feb 26, 2025
20 checks passed
@vathpela vathpela deleted the show-nx-compat-in-hsi branch February 26, 2025 00:40
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