Comment # 25 on bug 1153847 from Arnav Singh

I also have an ASRock motherboard (X399 Phantom Gaming 6). For some reason,
I do *not* have any problem booting after enabling SecureBoot. SB is enabled
in the mobo firmware settings, the OS was loaded via UEFI, and `dmesg` confirms
"Secure boot enabled" and "Loaded X.509 cert 'openSUSE Secure boot Signkey:
..."
I'm not sure why I did not have a problem given that MokManager never showed up
to ask me to accept openSUSE's signing cert.

That said, I definitely have the problem that MokManager doesn't render,
which is preventing me from doing `mokutil --disable-validation` /
`mokutil --enable-validation`. I tried pressing the keys blindly as described
in
[1] but it does not work; I assume I have the second answer's layout (the one
that asks for individual characters of the password) but I don't see a reboot
happening after pressing the final Enter according to that answer.

Upstream closed the issue with a fix [2] but then seems to have force-pushed it
out of history because they did not mean to release it just yet, so they have
a new PR [3]. It's not clear when they plan to release a version with that fix.

Could OpenSUSE patch in that PR for the sake of us ASRock users? If I
understand
correctly, me building the shim rpm locally with rpmbuild would not work
because
it would not be signed by Microsoft's key. If that's wrong and it would work
fine, then please say so and I'd be happy to test it with the patch applied.
But since the original author of #271 tested it on their ASRock board, I assume
it'll work correctly.

[1]:
https://askubuntu.com/questions/950395/mok-management-will-not-load-on-boot
     (both the first and second answers).

[2]: https://github.com/rhboot/shim/pull/271

[3]: https://github.com/rhboot/shim/pull/428