← Feed

Posts

• Post #4375015

  I'm pleased to announce that #NVIDIA is now supporting the #LVFS as a premier sponsor. The rollout of the NVIDIA DGX Spark firmware using #fwupd is going very well indeed, with downloads continuing to increase every day. This now takes us to 4 OEMs sponsoring LVFS, which means we've successfully reached the funding target we set for ourselves last year. More exciting announcements coming soon!

• Post #4318121

  What would you rather see in the output of fwupdmgr security?

• Post #4318120

  If anyone has an ideological problem with @whot adding a rustc dep to #fwupd now is the time to squeak.

• Post #4318119

  There are two types of people: Those that understand why your audio stutters when deploying an efivar-based certificate update (e.g. dbx) and those that don't. Both are interesting at parties, but never ask the first type to explain what they do as a job.

• Post #4318118

  I've just released https://github.com/hughsie/libxmlb/releases/tag/0.3.29 and https://github.com/fwupd/fwupd/releases/tag/2.1.7 with lots of great fixes and a smattering of new functionality. Enjoy!

• Post #4167183

  I've just tagged #passim 0.1.12 with a few nice low-priority security fixes -- certainly nothing earth shattering. https://github.com/hughsie/passim/releases/tag/0.1.12

• Post #3554231

  It seems the AI slop issues for fwupd just slowed down after all the Mythos fixes went in, rather than stopped. I guess we need to document that low severity "theoretical" security issues found using AI without a reproducer are not going to get CVEs. Does anyone see any problem in something like: https://github.com/fwupd/fwupd/pull/10604/changes -- it's wildly opinionated but perhaps pragmatic. Opinions welcome.

• Post #2486242

  #fwupd 2.0.5 hot on the heels of the last release: https://github.com/fwupd/fwupd/releases/tag/2.0.5 It's got a lot of fixups for dbx deployment failures we saw in the real world. Some people wonder what we do with the LVFS JSON report metadata that gets uploaded, and this is the answer -- we see patterns, write known issue pages on the LVFS wiki and then fix the code for the next release. This release has 3 such fixes. :)

• Post #2278245

  I'm at #PremDay at Paris and just walked past two people in the hallway I've never met in my life talking excitedly about #LVFS and #fwupd. I know it's an unusual niche open source project but it was a super proud moment for me. Open source maintenance is 99% fixing bugs and little things like this make it all worthwhile. Thanks those 2 random people!

• Post #2096088

  Both #Dell and #Lenovo have agreed to be premier sponsors for the #LVFS as part of our new sustainability effort. Over 145 million firmware updates have been deployed now, from over a hundred different vendors to millions of different Linux devices. With the industry support from Lenovo and Dell (and #Framework, OSFF, and of course both the Linux Foundation and Red Hat) we can build this ecosystem stronger and higher than before; we can continue the great work we've done long into the f...

• Post #1945054

  In less-awesome news somebody is now impersonating me on GitHub. If you see anything from "Richard Hughes jr" with an AI version of me as a profile photo -- it's obviously not me. I'm certainly not promoting any kind of cryptocurrency and I'm certainly not a believer in NWO or the Illuminati of all things. I wish I was making all this up... and what a weird timeline we live in.

• Post #1945053

  Does any of my network work for #GitHub? I'd like to ask if it's possible to make ticket ID 4303160 a priority. I'll happily swap it for some LVFS swag or to prioritise a specific fwupd bug! Someone crazy is impersonating me and dragging my name and profile image into all kinds of crypto and illuminati stuff. Thanks!

• Post #1945052

  I'm super impressed with the reviews from @coderabbitai -- they're an order of magnitude better than Claude (and two orders of magnitude better than copilot) even with the latest models. And free for open source projects! @coderabbitai how do I refer to you in a commit? e.g. "Co-Authored-By: coderabbitai" perhaps? Claude uses "Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>" if that helps.

• Post #1945051

  I've just tagged #fwupd 2.1.2, with lots of fixes, new hardware support and a few cool new features. See https://github.com/fwupd/fwupd/releases/tag/2.1.2 for the list. Enjoy!

• Post #1907631

  Hello again internet friends. What's the 2026 state of the art for syncing two folders on two different machines. e.g. like Dropbox used to be. It doesn't have to sync offline, but bonus points if it syncs to my Proton Drive too. I want to be able to change and add content to folders on either machine. There's no need to recover previous versions as I already back up in a different way. I used to use Unison for this a decade ago, but I wanted something that just works w...

• Post #1287409

  How is there no standard MiB constant of 1024*1024 in the C standard? What do other codebases do?

• Post #1287408

  Is everyone getting horseshit responses from #claude today? Queries that worked fine on Friday generate nonsense today.

• Post #1287407

  I'm pondering some interesting talks I could suggest for #OSFC this year. Does anyone want me to talk about anything specific for firmware, #fwupd or LVFS topics? I'm thinking doing a pretty aggressive FU aiming at some of the major hardware vendors, but I'm not sure my boss would approve. Other ideas welcome.

• Post #1287406

  What do you want to see in the fwupdmgr CLI when there's a long (5 minutes+) delay? Showing a progress bar means it's "stuck" on a specific character block for some time, and it'd would be easy to think that the process has hung. A spinner that goes back and forth with some kind of time estimation? Anything better?

• Post #1156985

  Announcing #fwupd 2.1.1 -- a very big release with the usual bugfixes, new features and lots and lots of new hardware support: https://github.com/fwupd/fwupd/releases/tag/2.1.1

• Post #1156859

  I've been (ab?)using Claude to find bugs in my software, and although it's found quite a few false positives, it's also found a lot of actual real bugs. Nothing CVE-worthy, but still important to fix. Releases include: * passim: https://github.com/hughsie/passim/releases/tag/0.1.11 * libxmlb: https://github.com/hughsie/libxmlb/releases/tag/0.3.26 * libjcat: https://github.com/hughsie/libjcat/releases/tag/0.2.6 #fwupd will follow, when all ^^^ has hit the various build-r...

• Post #457598

  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 https://fwupd.org/ and also the new "sponsorship pill" on various vendor pages like https://fwupd.org/lvfs/vendors/#framework

• Post #392743

  If the LVFS stopped signing with GPG+PKCS#7 and only relied on PKCS#7 going forward would anyone care? Thanks to using libjcat we can add and remove signature formats as we need to in a forwards and backwards compatible way. We added PQC-compatible certs a few months ago and nobody noticed.