Bug Description

[Impact]
On install and upgrade, shim-signed prompts users for disabling Secure Boot if DKMS packages are installed. The prompting was confusing, hard to see, and defaulted to not disabling Secure Boot.

[Test case]
(re-enable Secure Boot if necessary: 'sudo mokutil --enable-validation' and reboot)
1) Update shim-signed on a system with dkms packages installed, where Secure Boot is enabled.
Verify that as a first step you see an explanation of why you see the prompt (Secure Boot is enabled and you have third-party drivers).

Also:
Test upgrade from other release with DKMS packages installed, where Secure Boot is enabled; verify that you are prompted to disable Secure Boot, that the Disable Secure Boot checkbox is checked by default, and that you see an explanation text as a first step.

[Regression Potential]
This changes the default selection for disabling Secure Boot (picked by default), so quickly hitting "Next" will now move to prompting for the Secure Boot password to disable validation in shim; this breaks any users relying on blindly ignoring the prompts. Disabling Secure Boot will reduce the security of the system since it is no longer verified by UEFI signatures past loading the shim bootloader. In a true regression potential; should there be an issue with the prompting workflow in debconf, the usage of the debconf frontend may be impacted (for example, some particular frontend of debconf may fail (readline?))

---

Current strings in debconf templates for asking for a Secure Boot password are suboptimal:

Template: shim/secureboot_key
Type: password
_Description: Password:
Please enter a password for disabling Secure Boot. It will be asked again
after a reboot.

Template: shim/secureboot_key_again
Type: password
_Description: Re-enter password to verify:
Please enter the same password again to verify you have typed it correctly.

This would show only the short description in the debconf GNOME frontend; which may not be passing sufficient information for users to understand what is expected of them, and that they really need to remember that password since it will be asked after a reboot.

Related branches

I think we'll also want to use this bug report to track improvements to other aspects of the prompting, such as showing the large Secure Boot explanation text that is hidden behind the Help button otherwise.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

The verification of the Stable Release Update for shim-signed has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.