[Bug 1961864] Re: fwupd daemon failed verifying firmware signature

[Mario Limonciello]

** Changed in: fwupd (Ubuntu Focal)
       Status: Triaged => Invalid

** Changed in: fwupd (Ubuntu Impish)
       Status: Triaged => Invalid

** Changed in: fwupd (Ubuntu Jammy)
       Status: Fix Released => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to libjcat in Ubuntu.
https://bugs.launchpad.net/bugs/1961864

Title:
  fwupd daemon failed verifying firmware signature

Status in OEM Priority Project:
  Triaged
Status in fwupd package in Ubuntu:
  Invalid
Status in libjcat package in Ubuntu:
  Fix Released
Status in fwupd source package in Focal:
  Invalid
Status in libjcat source package in Focal:
  Triaged
Status in fwupd source package in Impish:
  Invalid
Status in libjcat source package in Impish:
  Triaged
Status in fwupd source package in Jammy:
  Invalid
Status in libjcat source package in Jammy:
  Fix Released

Bug description:
  The firmware blobs in cabinet archive are presently LVFS signed with
  gpg and pkcs7, if libjcat at compilation time without one then the
  blobs signed with both can't be verified.

  Impact is fwupd daemon will fail the firmware install immediately
  because OnlyTrusted=true is defaulted (in fwupd 1.7.x) to verifying
  the signature for daemon.

  We need uprev libjcat at least 0.1.4 onward to fix this issue.

  Issue is reproducible with fwupd 1.7.4
  -> https://launchpad.net/~ycheng-twn/+archive/ubuntu/fwupd174

  $ fwupdmgr --version
  client version:	1.7.4
  compile-time dependency versions
   gusb:	0.3.4

  daemon version: 1.7.4

  $ dpkg -l | grep libjcat
  ii  libjcat1:amd64    0.1.3-2   amd64   JSON catalog library

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1961864/+subscriptions