Create a new target lenovo-x1-carbon-gen11-uki#1630
Create a new target lenovo-x1-carbon-gen11-uki#1630alextserepov wants to merge 1 commit intotiiuae:mainfrom
Conversation
Absolutely. I will happily squash it as soon as I get it through pre-checks. :D |
QA will test it as part of secure boot testing, not this one specifically. |
88acece to
eede1b9
Compare
Signed-off-by: Aleksandr Tserepov-Savolainen <aleksandr.tserepov-savolainen@unikie.com>
ba890b6 to
8123903
Compare
|
Please update the testing instructions @alextserepov |
Sure. Done. |
|
Tested In both cases ghaf booted to emergency mode. |
Description of Changes
Create a new target lenovo-x1-carbon-gen11-uki with a UKI-enabled EFI partition.
At the moment, we generate the UKI in CI, which technically violates SLSA principles because it modifies the image after the build step. Although UEFI signing is also a form of post-build modification, introducing this new target ensures that signing becomes the only such change, thereby minimizing CI-side modifications and improving alignment with SLSA requirements.
We are introducing this as a separate target for testing purposes. If this approach proves successful, we may later update the existing x86_64 targets to produce UKI images directly.
Type of Change
Related Issues / Tickets
https://jira.tii.ae/browse/SSRCSP-7187
Checklist
make-checksand it passesTesting Instructions
Applicable Targets
aarch64aarch64x86_64x86_64x86_64Installation Method
nixos-rebuild ... switchTest Steps To Verify:
This PR introduces a new target that makes significant changes to the EFI partition and may therefore impact the boot process. After a successful boot, the system is expected to behave identically to the existing lenovo-x1-carbon-gen11-debug target. For this reason, testing should focus primarily on validating the boot flow and early startup behaviour.
To build the new target, run:
nix build .#lenovo-x1-carbon-gen11-uki-debug
Test procedure
Alternative testing
Basic boot validation tests may be performed instead of manual testing.