© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
Verifying existing binaries with new sbsigntool:
# wget http://
# wget http://
# sbverify --cert ./uefi.crt ./fwupx64.
warning: data remaining[63352 vs 71400]: gaps between PE/COFF sections?
Signature verification OK
# wget http://
# sbverify --cert ./uefi.crt ./fwupia32.
warning: data remaining[54648 vs 63512]: gaps between PE/COFF sections?
Signature verification OK
# wget http://
# tar xvf linux-signed.tar.gz
# sbverify --cert uefi.crt 4.15.0-
warning: data remaining[8249064 vs 8249080]: gaps between PE/COFF sections?
Signature verification OK
# sbverify --cert uefi.crt 4.15.0-
warning: data remaining[8298216 vs 8298232]: gaps between PE/COFF sections?
Signature verification OK
# wget http://
# sbverify --cert uefi.crt grubx64.efi.signed
Signature verification OK
# wget http://
# sbverify --cert uefi.crt ./grubaa64.
Signature verification OK
All existing bionic signatures validate correctly. Thus the problem is really induced by gaps/ordering of the .sbat & .data sections, on arm64 with the very new sbat-capable binaries.