Comment 36 for bug 1792575

Verification-done with shim-signed in xenial-proposed:

ii shim-signed 1.33.1~16.04.3+15+1 amd64 Secure Boot chain-loading bootloader (Microsoft-signed binary)

I've checked that a Secure Boot-enabled system correctly validates the shim binary that gets installed to disk, that it's the correct binary (Shim 15, commit 3beb971b), and that MokManager can successfully run (importing a cert). I've also checked that as per the expected changes, package installation of the new version of shim-signed insists on having grub2 2.02~beta2-36ubuntu3.20 installed as well.

ubuntu@lucky-moth:~$ sudo hexdump -Cv /boot/efi/EFI/ubuntu/shimx64.efi | grep -A 5 -B 5 \$Ver
sudo: unable to resolve host lucky-moth: Connection refused
000bf9b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000bf9c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000bf9d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000bf9e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000bf9f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000bfa00 55 45 46 49 20 53 48 49 4d 0a 24 56 65 72 73 69 |UEFI SHIM.$Versi|
000bfa10 6f 6e 3a 20 31 35 20 24 0a 24 42 75 69 6c 64 4d |on: 15 $.$BuildM|
000bfa20 61 63 68 69 6e 65 3a 20 4c 69 6e 75 78 20 78 38 |achine: Linux x8|
000bfa30 36 5f 36 34 20 78 38 36 5f 36 34 20 78 38 36 5f |6_64 x86_64 x86_|
000bfa40 36 34 20 47 4e 55 2f 4c 69 6e 75 78 20 24 0a 24 |64 GNU/Linux $.$|
000bfa50 43 6f 6d 6d 69 74 3a 20 33 62 65 62 39 37 31 62 |Commit: 3beb971b|