Lanzatool skips already existing files even if they are not signed #39
Labels
No labels
bug
dependency
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
review-next
security
stub
tool
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: raito/lanzaboote#39
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
If you remove a sig of a systemd-bootx64.efi, lanzatool will turn a blind eye and not sign it.
Causing surprising behaviors such as security violation :-((((
sd-boot is not signed by lanzatool if it already existed
same for kernels or any file actually I think
Yes, but for sd-boot it matters even on an "ignore" policy where we ignore old kernels and initrds
Related to #56 and #55.
Can't we just verify signature of existing files and sign them too, instead of just signing only non-existing files?
Yes this is what is planned.
#76 solved our issue with newer/malformed/unsiged systemd-boot binaries. It did not solve the issue with existing unsiged kernels.
#75 & Implementing a solution for #68 will fix this issue.
Hit this and one more
nix-collect-garbage -d
and anotherrebuild
solved this for me.Now that #75 is merged, the only issue left here is that the stub/UKI might not be signed and will not be resigned or overwritten. This, however, could only happen if the user manually removed the signature from one of them.