Not clear if it's the same issue, but on a Thinkpad T14s, new shim fails
to boot anything except the Canonical-signed grub. Both hash and key
MOKs seem to be ignored (blue screeen with Security Violation 0x1A for
signed executables). Downgrading to the version of shim-signed specified
in the initia
I just got hit by this. While 'ad_gpo_access_control = permissive' lets
users log in again, it is not ideal.
It appears that Samba AD does not create GptTmpl.inf except for policies
which actually set something in "Security Settings". Hence a policy with
nothing no security settings will not have
1.5 years on this is still broken: connectivity-check.ubuntu.com has no
record.
Workaround: remove network-manager-config-connectivity-ubuntu and
install network-manager-config-connectivity-debian instead.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
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: github.com/rhbo
