| Age | Commit message (Collapse) | Author |
|
VD tracker project renamed to NOS (2026-07) - PR titles and commit headlines
using the new NOS- key must stop being flagged invalid-task-id; legacy VD-
keys stay accepted. Fleet replication of canary vyos/vyos-1x#5379, whose
adversarial review tightened the regexes to ASCII [0-9] + literal-space.
🤖 Generated by [robots](https://vyos.io)
|
|
T8966: add legacy-label escape to invalid-task-id rule (commit check exempt)
|
|
|
|
T8966: extends central vyos/mergify + product T-ID rule
|
|
Onboard vyos/shim-signed to the central Mergify baseline via
`extends: mergify` and add the bot-excluded per-repo
`invalid-task-id` rule, matching the 49-repo IS-531 product fleet.
The 5 merge-protection gate labels were pre-created. Products
already enabled; no central-config change. Validated via the
Mergify config-simulator (200 OK). Rule body byte-identical to
the fleet canonical.
🤖 Generated by [robots](https://vyos.io)
|
|
|
|
the changes in 1.49 did not take into account the "SecureBoot enabled"
case when adding a default error trap. Closes: #1137098, #1137101.
|
|
Cope with "Platform is in Setup Mode" message
If we get any other unexpected output, print what we got for debugging.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
And link to a wiki page for more info. Need to write that page!
|
|
It's safer to do it here before a new shim is installed.
As we don't have any files installed at this point, we can't look up
knowwn signatures from a file. Instead, we now substitute the
signature fingerprints directly into shim-signed.preinst at package
build time.
Put the postinst back to where it was before the signature checks were
added.
|
|
If we have a sig from a key listed in DBX, don't just ignore
it. Firmware should refuse to boot things in a revoked chain so we
should fail here too.
Tweak the output too - switch from using a boolean $SAFE value to
using an error string in $SB_BOOT_ERROR so we can have more specific
errors printed.
|
|
|
|
If SecureBoot is enabled, check that our shim binary is signed by at
least one of the certificates enrolled in firmware.
|
|
Later, install that data alongside the shim binaries in the package.
We can then use this data to check that we can boot the signed shim
we're installing.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Found at
https://github.com/microsoft/secureboot_objects/blob/main/PreSignedObjects/DB/Certificates/microsoft%20uefi%20ca%202023.der
and copied here in PEM format, ready to use.
|
|
|
|
from multiple signed shims.
* Move the verification logic out into a new helper script
verify_combine_sigs - see comments there for how it works.
* Rename the existing shim binaries and CA cert to match
* Include some extra certs and binaries for testing with
|
|
If we have DKMS modules installed:
+ Check to see if a DKMS MOK key has been created and enrolled;
+ Check that all the DKMS modules are signed with that key;
If successful, don't tell users to disable Secure Boot.
Closes: #1108278.
Add dependencies on openssl and kmod for shim-signed-common,
needed for implementing these check.
|
|
|
|
Add changelog entries for merged changes
|
|
Update/add Catalan po-debconf translation
See merge request efi-team/shim-signed!4
|
|
Add alternative dependencies on systemd-boot
See merge request efi-team/shim-signed!3
|
|
|
|
|
|
With helpful fixes from Fabian Grünbichler
|
|
fix shim-helpers substvar handling
See merge request efi-team/shim-signed!2
|
|
else DEB_HOST_ARCH is not potentially not yet set and some invocations might
print a spurious warning.
Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
|
|
else the dpkg-query doesn't work.
Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
|
|
|
|
using substvars to make things more automatic in future.
|
|
|
|
|
|
|
|
Update build-dep on shim-unsigned to use 15.8-1.
Update SBAT to revoke grub binaries with sbat < 4.
Stop building for i386.
|
|
thanks to Remus-Gabriel Chelu. Closes: #1039090
|
|
Closes: #1042964, #1041449, #932358
|
|
|
|
|