You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit a4b9bae
Browse filesBrowse the repository at this point in the historyBrowse files
feat(ukisign): sign an unsigned ISO with cryptosctl image sign (#384)
cryptosctl image sign now takes an unsigned ISO as well as a UKI. It signs the UKI inside it the same way and writes it back over every copy, the El Torito EFI boot image's BOOTX64.EFI and the ISO 9660 file the installer copies, in pure Go with no root and no xorriso. The signed UKI and its .sig are written beside the ISO for staging upgrades.
Refs CryptOS-PKI/cryptos-appliance#83
Signed-off-by: Bugs5382 <12115015+Bugs5382@users.noreply.github.com>
Co-authored-by: Bugs5382 <12115015+Bugs5382@users.noreply.github.com>
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -75,7 +75,7 @@ task e2e:kind # Linux + docker: cert-manager in kind gets a certificate over
75
75
76
76
This repo builds no bootable image. The hardened kernel, SquashFS rootfs, UKI assembly, Secure Boot signing, the installer ISO and the QEMU + `swtpm` integration suites all live in [`cryptos-appliance`](https://github.com/CryptOS-PKI/cryptos-appliance), which requires this module at a pinned version and builds `init`, `cryptosctl` and the console by import path. See that repo's README and `docs/secure-boot.md` for building, signing and Secure Boot key custody.
77
77
78
-
The release assets are unsigned and carry no upgrade anchor. `cryptosctl image sign --image <unsigned.uki> --key <key.pem> --cert <cert.pem>` signs one with your own Secure Boot key and adds your certificate as its upgrade anchor, so a node installed from it takes signed in-place upgrades. [`docs/image-sign.md`](docs/image-sign.md) covers it.
78
+
The release assets are unsigned and carry no upgrade anchor. `cryptosctl image sign --image <unsigned.uki> --key <key.pem> --cert <cert.pem>` signs one with your own Secure Boot key and adds your certificate as its upgrade anchor, so a node installed from it takes signed in-place upgrades. Given an unsigned ISO, it signs the UKI inside it and writes a signed ISO. [`docs/image-sign.md`](docs/image-sign.md) covers it.
0 commit comments