This bug was fixed in the package secureboot-db - 1.4~ubuntu0.18.04.1
---
secureboot-db (1.4~ubuntu0.18.04.1) bionic; urgency=medium
* Backport secureboot-db from cosmic to apply the August 2016 dbx updates
from Microsoft. LP: #1776996.
-- Brian Murray Fri, 19 Oct 2018
This bug was fixed in the package secureboot-db - 1.4~ubuntu0.16.04.1
---
secureboot-db (1.4~ubuntu0.16.04.1) xenial; urgency=medium
* Backport secureboot-db from cosmic to apply the August 2016 dbx updates
from Microsoft. LP: #1776996.
-- Brian Murray Fri, 19 Oct 2018
This bug was fixed in the package secureboot-db - 1.4~ubuntu0.14.04.1
---
secureboot-db (1.4~ubuntu0.14.04.1) trusty; urgency=medium
* Backport secureboot-db from cosmic to apply the August 2016 dbx updates
from Microsoft. LP: #1776996.
-- Brian Murray Fri, 19 Oct 2018
The trusty package from -proposed also successfully installed on a BIOS
system.
bdmurray@clean-trusty-amd64:~$ sudo apt install secureboot-db
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no
Installing the version of secureboot-db from trusty-proposed on an UEFI
system with secureboot enabled was also successful and the new keys were
added to the filesystem.
** Attachment added: "trusty-bug176996-withsb.png"
Installing version of secureboot-db from trusty-proposed on an UEFI
system without secureboot was successful and new keys were added to the
filesystem.
** Attachment added: "trusty-bug176996.png"
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776996
Title:
secureboot-db out of date, missing revocations from
The xenial package from -proposed also successfully installed on a BIOS
system.
bdmurray@clean-xenial-amd64:~$ sudo apt install secureboot-db
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no
Installing the version of secureboot-db from xenial-proposed on an UEFI
system with secureboot enabled was also successful and the new keys were
added to the filesystem.
** Attachment added: "xenial-bug176996-withsb.png"
Installing the version of secureboot-db from xenial-proposed on an UEFI
system without secureboot was successful and new keys were added to the
filesystem.
** Attachment added: "xenial-bug176996.png"
The bionic package from -proposed also successfully installed on a BIOS
system.
bdmurray@clean-bionic-amd64:~$ sudo apt install secureboot-db
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
secureboot-db
1
Installing the version of secureboot-db from bionic -proposed on an UEFI
system with secureboot enabled was also successful and the new keys were
added to the filesystem.
** Attachment added: "bionic-bug176996-withsb.png"
Installing version of secureboot-db from bionic -proposed on an UEFI
system without secureboot was successful and new keys were added to the
filesystem.
** Attachment added: "bionic-bug176996.png"
The package successfully installed and upgraded on a bionic container:
The following packages will be upgraded:
secureboot-db
1 upgraded, 0 newly installed, 0 to remove and 49 not upgraded.
Need to get 8488 B of archives.
After this operation, 21.5 kB disk space will be freed.
Get:1
Hello Steve, or anyone else affected,
Accepted secureboot-db into trusty-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/secureboot-
db/1.4~ubuntu0.14.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Hello Steve, or anyone else affected,
Accepted secureboot-db into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/secureboot-
db/1.4~ubuntu0.16.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Hello Steve, or anyone else affected,
Accepted secureboot-db into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/secureboot-
db/1.4~ubuntu0.18.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
** Description changed:
- A signed variable update for secureboot dbx has been published by
- Microsoft to uefi.org; last updated 2016-08-11:
- http://www.uefi.org/sites/default/files/resources/dbxupdate.zip
+ Impact
+ --
+ A signed variable update for secureboot dbx has been published by
** Also affects: secureboot-db (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: secureboot-db (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: secureboot-db (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in:
@vorlon - seems this might be causing a failure - see #1791248
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776996
Title:
secureboot-db out of date, missing revocations from Aug 2016
To manage
This bug was fixed in the package secureboot-db - 1.2
---
secureboot-db (1.2) cosmic; urgency=medium
* Apply the August 2016 dbx updates from Microsoft. LP: #1776996.
* chattr -i the EFI variables before trying to call sbkeysync, since the
kernel now has these files
** Tags added: id-5b22e55970e8360b88ce82be
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776996
Title:
secureboot-db out of date, missing revocations from Aug 2016
To manage notifications about
Error in testing:
New keys in filesystem:
/tmp/keys/dbx/dbxupdate.bin
Inserting key update /tmp/keys/dbx/dbxupdate.bin into dbx
Can't create key file
/sys/firmware/efi/efivars/dbx-d719b2cb-3d3a-4596-a3bc-dad00e67656f: Operation
not permitted
Error syncing keystore file
23 matches
Mail list logo
