On Fri, Mar 17, 2017 at 03:52:28PM -0000, Mathieu Trudel-Lapierre wrote:
> What is the content of the following files?
> /proc/sys/kernel/secure_boot
> /proc/sys/kernel/moksbstate_disabled
This shouldn't matter for solving this bug. I believe the only thing you
need is, at line 83 when checking the secureboot_key values:
if [ -z "$key" ] && [ -z "$again" ] && \
! db_fget shim/${action}_secureboot seen && \
! db_fget shim/secureboot_key seen
then
echo 'no key given in non-interactive mode; doing
nothing'
exit 0
fi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1673817
Title:
update-secure-boot-policy behaving badly with unattended-upgrades
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1673817/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
