toad.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Mastodon server operated by David Troy, a tech pioneer and investigative journalist addressing threats to democracy. Thoughtful participation and discussion welcome.

Administered by:

Server stats:

275
active users

#fwupd

3 posts2 participants0 posts today

New #fwupd release just dropped: github.com/fwupd/fwupd/release

It fixes the bug (mea culpa) where the KEK failed to deploy correctly. If you had a KEK deploy failure, please update to this release and try again. I'll re-upload the KEKs to the LVFS with the fwupd requirement set to 2.0.10.

There's also some other better stuff, so enjoy!

GitHubRelease 2.0.10 · fwupd/fwupdThis release adds the following features: Include the AGESA version as the summary of the AMD secure processor device Include the UEFI PK certificate key ID in the uploaded problem report Provide ...

Edit: seems to be resolved now

Anyone else getting fwupdmgr checksum errors right now?

$ fwupdmgr refresh --force
Updating lvfs
Downloading… [************************************** ]
Failed to update metadata for lvfs: checksum failure: failed to verify data, expected ffbee0c4af245985093489884ef435767f1fd919

Replied in thread

I didn't think that Daniel Micay / GrapheneOS would already be targeting new victims and hé will be just continuing to attack /e/, but I was wrong.
The #fwupd developer is being targeted, and #grapheneos has shown no evidence of Richard's harassment of him and GOS.
Please support Richard @hughsie who is being accused of being hostile to #GOS without any proof.

GrapheneOS has serious problems with fwupd

GrapheneOS is a privacy-focused operating system for Android phones that aims to increase your privacy while maintaining basic Android functions. This is built for Google Pixel phones as they meet the project’s requirements.

The official GrapheneOS project has just recently released a statement on their official Mastodon account stating that they have become aware of an issue with the fwupd program, which is a firmware update service for computers that are running Linux, such as Ubuntu, Debian, Red Hat, Fedora, Gentoo, Arch Linux, and more. It has become evident that the fwupd program has been incorrectly connecting to random USB devices using the Fastboot protocol.

As a result, users will experience an error when trying to connect to the USB device because the system would be reporting that the USB device is already in use. The GrapheneOS project has considered this issue to be a group of fatal bugs, because they “can block an installation part of the way through and lead to an unusable device until the user fixes it.” They have also called this practice “wrong,” because the main use of Fastboot would be broken.

As a workaround, we recommend following the official guidelines to make sure that fwupd stops trying to connect to random USB devices that the project team have documented via the following pages:

We hope that the fwupd program gets an update that will fix this bug.

wellllll not the cleanest code I ever wrote, but all things considered I'm pretty happy with this. It enables capsule updates for all Qualcomm devices (supported in upstream), without needing a table of devices, and supporting multiple boot methods (since some devices can have run u-boot either as the first stage bootloader or chainloaded)

once this and some other bits are in, we can start the process of getting builds for some different smartphones onto #fwupd / #lvfs so you can not just have an EFI bootloader on your OnePlus 6, but it can get updates too regardless of which distro you're running :D

lore.kernel.org/u-boot/2025032

lore.kernel.org[PATCH 2/4] mach-snapdragon: CapsuleUpdate: support all boot methods - Caleb Connolly

A new #fwupd 2.0.7 release just dropped; the new 5G modem stuff wasn't quite ready for this release but I'll hopefully make 2.0.8 -- but there are plenty of other nice things to play with while you wait: github.com/fwupd/fwupd/release

Important heads up! We removed a ton of build configuration options this release (removing ifdefs and complexity from the code) so you might need to tweak any downstream build files.

GitHubRelease 2.0.7 · fwupd/fwupdThis release adds the following features: Allow calling 'fwupdtool security' with a fwupd version parameter A new plugin to update B&R DisplayPort receivers A new plugin to update Intel CVS camera...

I've just tagged #fwupd 2.0.4 -- lots of nice new features, and most importantly with new protocol support to allow applying the latest dbx security update: github.com/fwupd/fwupd/release

As to why we need a new protocol, I'm about to start writing a blog explaining why we couldn't just use the existing uefi-dbx plugin. I'll link to this post when it's done.

If I see lots of dbx updates going out with 2.0.4 in the next few hours I'll also backport the new protocol into 1_9_X for 1.9.27

GitHubRelease 2.0.4 · fwupd/fwupdThis release adds the following features: Record the entire USB descriptor in the emulation data Return defined return code when network metadata refresh fails This release fixes the following bu...