My understanding from vorlon's comment is that this is fixed in current
shim in groovy (and releases' -proposed pockets), so closing.
** Changed in: shim-signed (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Yes, I have just crashed into this.
My system is now totally secure. To the point where it is impossible to get
past this boot up screen to actually log in.
I can't do anything. I can't upgrade anything. I can't fix anything. I can't
access the boot disk. The box is not bricked.
Great work
The current shim in Ubuntu was built with 3.0.8. We have a signing
request pending for a new one which was built with newer gnu-efi
(3.0.9). So it sounds like this bug will be fixed as a matter of course
once that newer shim has been signed.
--
You received this bug notification because you
Seeing the same issue on a Hyper-V VM running 20.04. Workaround is to
enroll the MOK with mokutil.
Seems related to this bug: https://github.com/rhboot/shim/issues/143 .
While it was closed in 2018, maybe no one has recompiled shim-signed
with the fixed gnuefi?
** Bug watch added:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: shim-signed (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870955
Title:
** Changed in: shim-signed (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870955
Title:
MokManager - Only DER encoded certificate (*.cer/der/crt) is
** Attachment added: "kek.txt"
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1870955/+attachment/5351886/+files/kek.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870955
Title:
Manually steps in grub:
chainloader mmx64.efi, then "Enroll key from disk" ->
/var/lib/shim-signed/mok/MOK.der.
shim-signed/focal,now 1.40+15+1533136590.3beb971-0ubuntu1 amd64
In this case there is no problem with the certificate. I think there are two
possibilities:
MokManager or UEFI
** Attachment added: "db.txt"
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1870955/+attachment/5351887/+files/db.txt
** Description changed:
Installation of VirtualBox requires signing kernel modules.
During installation a certificate is generated. It should be
What were the steps you took to try to manually add the certificate?
The /var/lib/shim-signed/mok/MOK.der file that we populate is certainly
a DER-encoded certificate, and users have been successfully registering
these certificates through MokManager.
What version of the shim-signed package do
** Package changed: mokutil (Ubuntu) => shim-signed (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870955
Title:
MokManager - Only DER encoded certificate (*.cer/der/crt) is supported
To
11 matches
Mail list logo
