Bug 870144 - shim: revocations and "dbx" variable updates
shim: revocations and "dbx" variable updates
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: shim (Show other bugs)
18
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Matthew Garrett
Fedora Extras Quality Assurance
:
Depends On:
Blocks: 869613
  Show dependency treegraph
 
Reported: 2012-10-25 12:12 EDT by Florian Weimer
Modified: 2013-10-24 22:28 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-10-24 22:28:42 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Florian Weimer 2012-10-25 12:12:52 EDT
We need a way to revoke bad signatures, so that the signature on the "shim" EFI application doesn't have to be revoked, which would result in a lot of pain.

shim checks for revocations via the "dbx" variable (and provides a service to grub2), but we currently do not update the "dbx" variable, and we do not seem to be able to blacklist individual kernel modules.

The contents of the "dbx" variable is maintained externally and cryptographically protected, so we'll have to synchronize kernel and grub2 updates addressing Secure Boot issues with an external party.  Doing our own revocation processing in addition to the "dbx" checks seems preferable.

(This obviously extends beyond the shim component, but I want to file it somewhere so that this does not get lost.)
Comment 1 Peter Jones 2013-10-24 22:28:42 EDT
There's no actual bug here...

Note You need to log in before you can comment on or make changes to this bug.