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
I would like to report an issue with the re-signing process of a Limine EFI file after enrolling the config key. When trying to re-sign the file, I encounter an "Incorrect digest" error.
Steps to reproduce:
Sign the file using sbctl (work)
sbctl sign limine_x64.efi
But there is no option to reset the signature of this file.
Enroll a key of the Limine config into this EFI file to protect against modifying this config:
After enrolling the config key into the EFI file, I am unable to re-sign the file due to the "Incorrect digest" error.
It seems there is no option to reset the signature. I would like to know if there is a way to reset the signature or a workaround for this issue.
The text was updated successfully, but these errors were encountered:
In the case of a kernel update or installation (such as for initramfs or vmlinuz) without using UKI, this can cause a mismatch with the checksum inside the Limine EFI file, which is why the EFI file needs to be updated.
It would be inefficient for an automated process to check the source path of the original binary and replace the old file every time initramfs is built.
I just wanted to ask if it is possible to implement an option to reset the signature, nothing more. If it’s not possible, that’s fine with me. 🙂
I would like to report an issue with the re-signing process of a Limine EFI file after enrolling the config key. When trying to re-sign the file, I encounter an "Incorrect digest" error.
Steps to reproduce:
sbctl
(work)But there is no option to reset the signature of this file.
Enroll a key of the Limine config into this EFI file to protect against modifying this config:
Output:
Incorrect digest
Problem:
After enrolling the config key into the EFI file, I am unable to re-sign the file due to the "Incorrect digest" error.
It seems there is no option to reset the signature. I would like to know if there is a way to reset the signature or a workaround for this issue.
The text was updated successfully, but these errors were encountered: