Bug 1767143 - fwupd fails to install uefi updates with secure boot enabled
Summary: fwupd fails to install uefi updates with secure boot enabled
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: fwupd
Version: 31
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-30 19:09 UTC by Mario Limonciello
Modified: 2020-09-14 19:15 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-09-14 19:15:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github fwupd fwupd issues 1504 0 None closed uefi: Fails to install update with secure boot enabled in Fedora 2020-09-14 19:08:28 UTC

Description Mario Limonciello 2019-10-30 19:09:28 UTC
Description of problem:
Today, I received an update for "Latitude 7480 System Firmware" version 0.1.16.1.

After agreeing to reboot, a blue error screen appeared, saying

ERROR
Verification failed: (0x1A) Security Violation



Version-Release number of selected component (if applicable):
1.2.11

How reproducible:
Whenever secure boot on

Steps to Reproduce:
1. Turn on secure boot
2. Do UEFI firmware update
3. Reboot system

Actual results:

Fails to install

Expected results:

Installs

Additional info:
Reported upstream here: https://github.com/fwupd/fwupd/issues/1504

Diagnosed that signature in the build was wrong according to build log:
https://kojipkgs.fedoraproject.org//packages/fwupd/1.2.11/2.fc30/data/logs/x86_64/build.log

```
+ /usr/bin/pesign -c 'Red Hat Test Certificate' --certdir /etc/pki/pesign-rh-test -i /builddir/build/BUILDROOT/fwupd-1.2.11-2.fc30.x86_64/usr/libexec/fwupd/efi/fwupdx64.efi -o /builddir/build/BUILDROOT/fwupd-1.2.11-2.fc30.x86_64/usr/libexec/fwupd/efi/fwupdx64.efi.signed -s
+ '[' '!' -s -o /builddir/build/BUILDROOT/fwupd-1.2.11-2.fc30.x86_64/usr/libexec/fwupd/efi/fwupdx64.efi.signed ']'
```

Comment 1 Paulo Fidalgo 2019-11-11 11:18:57 UTC
I have the same problem with a Dell XPS 13 9380 System Firmware 0.1.8.0.

Comment 2 Dennis Schridde 2020-03-11 09:31:24 UTC
> Looking at https://kojipkgs.fedoraproject.org//packages/fwupd/1.2.11/2.fc30/data/logs/x86_64/build.log
> 
> I think the build server signed with the wrong cert in Fedora 30.
> 
> ```
> + /usr/bin/pesign -c 'Red Hat Test Certificate' --certdir /etc/pki/pesign-rh-test -i /builddir/build/BUILDROOT/fwupd-1.2.11-2.fc30.x86_64/usr/libexec/fwupd/efi/fwupdx64.efi -o /builddir/build/BUILDROOT/fwupd-1.2.11-2.fc30.x86_64/usr/libexec/fwupd/efi/fwupdx64.efi.signed -s
> + '[' '!' -s -o /builddir/build/BUILDROOT/fwupd-1.2.11-2.fc30.x86_64/usr/libexec/fwupd/efi/fwupdx64.efi.signed ']'
> ```
> 
> Compare that to Fedora 31: https://kojipkgs.fedoraproject.org//packages/fwupd/1.2.11/2.fc31/data/logs/x86_64/build.log
> 
> ```
> + /usr/bin/pesign-client -t 'Fedora Signer (OpenSC Card)' -c '/CN=Fedora Secure Boot Signer' -i /builddir/build/BUILDROOT/fwupd-1.2.11-2.fc31.x86_64/usr/libexec/fwupd/efi/fwupdx64.efi -o /builddir/build/BUILDROOT/fwupd-1.2.11-2.fc31.x86_64/usr/libexec/fwupd/efi/fwupdx64.efi.signed -s
> + '[' '!' -s -o /builddir/build/BUILDROOT/fwupd-1.2.11-2.fc31.x86_64/usr/libexec/fwupd/efi/fwupdx64.efi.signed ']'
> ```
> 
> (source: https://github.com/fwupd/fwupd/issues/1504#issuecomment-547082260)

Comment 3 Ben Cotton 2020-04-30 20:21:34 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Bryan Mason 2020-05-21 02:10:02 UTC
I just ran into this problem on a ThinkPad X1 Yoga (4th gen) running Fedora 31.

Comment 5 Richard Hughes 2020-09-14 19:15:10 UTC
If this still does not work on F32, can you file this upstream please and then I can tag the correct Dell engineers to fix this: https://github.com/fwupd/fwupd/issues -- thanks.


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