** Tags added: id-5bbd25580c30e754dd2d61ed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797011
Title:
[FFE] Update mokutil to fb6250f2
To manage notifications about this bug go to:
This bug was fixed in the package mokutil - 0.3.0+1538710437.fb6250f-
0ubuntu2~14.04.1
---
mokutil (0.3.0+1538710437.fb6250f-0ubuntu2~14.04.1) trusty; urgency=medium
* Backport mokutil 0.3.0+1538710437.fb6250f-0ubuntu2 to 14.04.
(LP: #1797011)
-- Mathieu Trudel-Lapierre
This bug was fixed in the package mokutil - 0.3.0+1538710437.fb6250f-
0ubuntu2~16.04.1
---
mokutil (0.3.0+1538710437.fb6250f-0ubuntu2~16.04.1) xenial; urgency=medium
* Backport mokutil 0.3.0+1538710437.fb6250f-0ubuntu2 to 16.04.
(LP: #1797011)
-- Mathieu Trudel-Lapierre
Verification-done for xenial: mokutil 0.3.0+1538710437.fb6250f-0ubuntu2~16.04.1
Verification-done for trusty: mokutil 0.3.0+1538710437.fb6250f-0ubuntu2~14.04.1
Verified that 'mokutil --reset', 'mokutil --export --db', 'mokutil --export
--mok' as well as setting a timeout via 'mokutil --timeout'
** Tags added: id-5bbd25580c30e754dd2d61ed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797011
Title:
[FFE] Update mokutil to fb6250f2
To manage notifications about this bug go to:
Hello Mathieu, or anyone else affected,
Accepted mokutil into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mokutil/0.3.0+1538710437.fb6250f-
0ubuntu2~16.04.1 in a few hours, and then in the -proposed repository.
Please help us by testing
This bug was fixed in the package mokutil - 0.3.0+1538710437.fb6250f-
0ubuntu2~18.04.1
---
mokutil (0.3.0+1538710437.fb6250f-0ubuntu2~18.04.1) bionic; urgency=medium
* Backport mokutil 0.3.0+1538710437.fb6250f-0ubuntu2 to 18.04.
(LP: #1797011)
-- Mathieu Trudel-Lapierre
** Description changed:
[Impact]
- All Ubuntu users on UEFI systems
+ Potentially any Ubuntu users on UEFI systems; as mokutil is used to control
from the userland the behavior of Secure Boot via shim.
+
+ New features have been introduced in mokutil that we'll want to make use
+ of in
> All Ubuntu users on UEFI systems
All Ubuntu users on UEIF systems...what?
Since I don't understand what bug is being fixed here, I'll move on. I
guess other SRU team members must understand the background already, so
I guess they can manage the release if they're satisfied, or if you want
to
Verification-done for mokutil 0.3.0+1538710437.fb6250f-0ubuntu2~18.04.1
on bionic:
I have verified that timeout, export, and reset / toggle-validation
features in mokutil all work, as a verification for the new features and
smoketesting for the existing features already in use.
When using
Hello Mathieu, or anyone else affected,
Accepted mokutil into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mokutil/0.3.0+1538710437.fb6250f-
0ubuntu2~18.04.1 in a few hours, and then in the -proposed repository.
Please help us by testing
This bug was fixed in the package mokutil - 0.3.0+1538710437.fb6250f-
0ubuntu2
---
mokutil (0.3.0+1538710437.fb6250f-0ubuntu2) cosmic; urgency=medium
* debian/patches/int-signedness.patch: Fix compile failure on
platforms where int != unsigned int.
-- Steve Langasek Wed, 10
FFe approved.
Test case not needed for an FFe, ignoring and have not reviewed.
** Changed in: mokutil (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797011
Package builds and installs fine (see attached build log):
╭─ mtrudel@demeter …/cosmic
╰─ sudo dpkg -i mokutil_0.3.0+1538710437.fb6250f-0ubuntu1_amd64.deb
[sudo] password for mtrudel:
(Reading database ...
THe principal feature we need here is --export; which will allow us to
export keys from the firmware and compare kernel signatures to figure
out whether kernels are signed with trusted keys, which will improve the
experience on upgrades from previous releases. This is especially
relevant in the
15 matches
Mail list logo