Skip to content

Append secure boot utility by adding expired and rootca cert generation - #20

Open
kiemonbb wants to merge 4 commits into
masterfrom
secure_boot_files
Open

Append secure boot utility by adding expired and rootca cert generation#20
kiemonbb wants to merge 4 commits into
masterfrom
secure_boot_files

Conversation

@kiemonbb

Copy link
Copy Markdown

No description provided.

…ge generation

Signed-off-by: Oktawian Bieszke <oktawian.bieszke@3mdeb.com>
Signed-off-by: Oktawian Bieszke <oktawian.bieszke@3mdeb.com>
@kiemonbb
kiemonbb requested a review from philipanda August 12, 2026 13:51
@kiemonbb
kiemonbb marked this pull request as draft August 12, 2026 13:51
Signed-off-by: Oktawian Bieszke <oktawian.bieszke@3mdeb.com>
@kiemonbb
kiemonbb marked this pull request as ready for review August 13, 2026 10:02
@kiemonbb

Copy link
Copy Markdown
Author

Log showing sbverify correctly verifies newly generated digital signatures.
sbverify.log

@philipanda

Copy link
Copy Markdown
Contributor

adding expired

Just a quick note before I review, have you considered the UEFI spec details @miczyg1 gave here? Dasharo/dasharo-issues#1863
Are the scripts generating certs that would correctly verify the mechanism that's actually expected by the UEFI spec? The test https://github.com/Dasharo/open-source-firmware-validation/blob/encrypted-rootfs-release-rebase/scripts/secure-boot/generate-images/sb-img-wrapper.sh and the script used for it https://github.com/Dasharo/open-source-firmware-validation/blob/encrypted-rootfs-release-rebase/scripts/secure-boot/generate-images/sb-img-wrapper.sh were testing something that is not true for UEFI compliant firmware.

@kiemonbb

Copy link
Copy Markdown
Author

Yes, I'm aware of Dasharo/dasharo-issues#1863, but this PR only intended to transfer utility from the lost sb-image-wrapper.sh file . The expired cert wasn't too much of a hassle to add and as @miczyg1 said it should still fail on UEFI compliant firmware.

@philipanda

Copy link
Copy Markdown
Contributor

The expired cert wasn't too much of a hassle to add and as @miczyg1 said it should still fail on UEFI compliant firmware.

It would require some more fields in the certificates and timestamping the signature, which sbsign does not support. If that's just a port then fine. As the scripts are tightly connected to OSFV tests I'd add a comment stating that the expired certs are currently not viable for testing the functionality. It would then be easier to not forget about that later.

@kiemonbb

Copy link
Copy Markdown
Author

I'd add a comment stating that the expired certs are currently not viable for testing the functionality. It would then be easier to not forget about that later.

Added note in readme https://github.com/Dasharo/osfv-test-data/pull/20/changes#diff-b2b6a9e250b262ad7ba45030f2bb02dd4be8f08a3c8f9220b1767cfa9b9e6d3bR30

Comment thread hello-dasharo/README.md Outdated
@kiemonbb
kiemonbb force-pushed the secure_boot_files branch 2 times, most recently from 903db11 to bd6766b Compare August 20, 2026 07:44
Comment thread hello-dasharo/Makefile
Comment thread hello-dasharo/signing/keygen.sh Outdated
Signed-off-by: Oktawian Bieszke <oktawian.bieszke@3mdeb.com>
@philipanda

Copy link
Copy Markdown
Contributor

Have you tried running the OSFV tests with these?

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