Richard Hughes

I'm also happy to announce we've got a new sponsor for the LVFS: #Framework Although there are about a half a dozen OEMs that have promised to sponsor LVFS, Framework is the first to have actually signed the paperwork. You can see the new logo on

LVFS: Home

and also the new "sponsorship pill" on various vendor pages like

LVFS: Vendor Status

I've just pushed the button and moved the #fwupd translations from Transifex to @Weblate We're planning a new release in a few days and it would be *wonderful* to get the translations looking beautiful before that. Thank you all my clever 2nd, 3rd and 4th language friends! All the new functionality is available here:

Making sure you're not a bot!

Does anyone want to help out with an important open source project like #fwupd? We're always short of reviewers to look at patches and provide comments -- and from personal experience -- reviewing other peoples code is a great way to pick up tips and tricks and make yourself a better programmer. If this sounds interesting, and a potential first step on an open source adventure let me know. Some of the PRs are simple and you don't need to be any kind of code wizard.

A new #fwupd release just dropped!

GitHub

Release 2.0.14 · fwupd/fwupd

This release adds the following features: Add support for ignoring the network connectivity requirement Allow building on RHEL-9 and RHEL-10 Allow...

with lots of new hardware supported and a lot of bugfixes for existing devices.

Current status: The LVFS is getting pillaged by an AI bot that's coming from *hundreds* of different IPs with a user agent of "Mozilla/5.0 (Windows NT 10.0; Win64; x64) Chrome/91.0.4472.124". I'm impressed the LVFS handled the load spike, but I'm also planning to add support for blocking by ASN today...

A few weeks ago I was invited to talk about firmware updates for servers using fwupd/LVFS at Prem'Day 2025. I gave the hardware vendors a really hard time, and got lots of instant feedback from customers in the the audience from the "little green thumbs" that people could raise. The main takeaway from the Prem’Day community seemed to be that proprietary tooling adds complexity without value, and using open ecosystems enable users to better operate their infrastructure.

Hey lazyweb -- can you please reply to this post with the output of this command on your system: strings -f -n 20 /sys/firmware/efi/efivars/{PK-*,db-*,KEK-*} | uniq I'm trying to make some future fwupd feature look pretty. Thanks!

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

Release 2.0.7 · fwupd/fwupd

This release adds the following features: Allow calling 'fwupdtool security' with a fwupd version parameter A new plugin to update B&R DisplayPort...

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.

Now I finally have a laptop model I can recommend when a customer wants to buy hardware that has to be supplied with an embedded firmware SBOM. Good job Framework!

LVFS: Laptop 13 AMD Ryzen AI 300

#opensource #sbom #firmware #framework

Does anybody know why people are scanning the LVFS in this weird way? There's several bots searching for weird device tokens every two seconds until they get auto-banned. Ideas?