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
Does a report exist for this bug with the project's home (upstream) and/or another distro?
No response
Expected behaviour
The packages should include a configurable hook in /etc/default, that allows a user to set the file path of the /etc/kernel.d script, so that UKIs or non standard vmlinuz paths can be affected by these hooks. The file /efi/EFI/BOOT/void/Linux-${VERSION} should be just as affected as the default /boot/vmlinuz-${VERSION}
Actual behaviour
Due to the hardcoded nature of the file paths, only /vmlinuz-${VERSION} is affected by these scripts.
Steps to reproduce
Install dracut-uefi and the affected packages (efibootmgr-18_1, sbsigntool-0.9.4_6)
configure the packages using /etc/default to your liking
run xbps-reconfigure -fa
Notice that the UKI neither gets registered by efibootmgr, nor gets signed by sbsigntool
The text was updated successfully, but these errors were encountered:
I'm currently working on updating the scripts. Only sbsigntool and efibootmgr are tested, other packages with a hook in /etc/kernel.d might be affected too.
piekay
changed the title
Some packages that have kernel.d are always trying to modify vmlinuz-${version} even if dracut-uefi is used.
Some packages that have kernel.d hooks are always trying to modify vmlinuz-${version} even if dracut-uefi is used.
Dec 2, 2024
Is this a new report?
Yes
System Info
Void 6.6.63_1 x86_64 AuthenticAMD uptodate rFF
Package(s) Affected
efibootmgr-18_1, sbsigntool-0.9.4_6
Does a report exist for this bug with the project's home (upstream) and/or another distro?
No response
Expected behaviour
The packages should include a configurable hook in /etc/default, that allows a user to set the file path of the /etc/kernel.d script, so that UKIs or non standard vmlinuz paths can be affected by these hooks. The file /efi/EFI/BOOT/void/Linux-${VERSION} should be just as affected as the default /boot/vmlinuz-${VERSION}
Actual behaviour
Due to the hardcoded nature of the file paths, only /vmlinuz-${VERSION} is affected by these scripts.
Steps to reproduce
The text was updated successfully, but these errors were encountered: