shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

244
active users

#fwupd

1 post1 participant0 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 ...

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

Continued 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.