[Bug 1934506] Re: Mirrored MOK variables could be accidentally deleted

[Łukasz Zemczak]

Hello Julian, or anyone else affected,

Accepted shim into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/shim/15.4-0ubuntu7 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: shim (Ubuntu Focal)
       Status: New => Fix Committed

** Tags added: verification-needed-focal

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to shim in Ubuntu.
https://bugs.launchpad.net/bugs/1934506

Title:
  Mirrored MOK variables could be accidentally deleted

Status in shim:
  New
Status in shim package in Ubuntu:
  Fix Released
Status in shim source package in Focal:
  Fix Committed
Status in shim source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]
  On some systems, Mok variables mirrored are accidentally deleted after the mirroring. This can prevent the kernel from loading DKMS modules, if it does not yet use the config table to parse the MokList variable; and userspace tools relying on the variables will have wrong results.

  Most implementations reject the accidental delete, as the flags do not
  match, this bug was produced on VMWare.

  [Test plan]
  If we can get a VMWare Workstation or Player license, it would be good to validate that. Without a license, the best we can do is ensure there are no regressions on other machines and rely on the authors of the patch (SUSE) to have tested this properly.

  [Where problems could occur]
  We could accidentally delete the variable on other systems now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/shim/+bug/1934506/+subscriptions