Instead, they sent documentation and got the Dev in touch with Logitech's internal dev team, and a Linux solution was born.
Would it have been cool if Logitech just did it from the get-go? Sure, but I think there is an element of "Cool" from Logitech's willingness to be a resource for the Linux community.
Logitech would get a much bigger warm fuzzy if they did this work themselves, but this is the next best thing.
f/loss is starting to look like religion as long as we have these arbitrary boundaries.
For people running Linux exclusively, like a lot of Red Hat’s customers
Some devices are plugged in behind racks of computers forgotten, or even hot-glued into place and unremovable
Shame to see list of supported/supporting vendors is so short: https://secure-lvfs.rhcloud.com/lvfs/devicelist
It's been a long journey but bit by bit, we're getting out of second class status.
What is really worrying is that this is 1 year old yet the unifying receiver which came with 2 products I bought a month ago from a larger retailer (AMZ DE) had an older FW. And while it is understandable that the stock AMZ has might be older than a year, what is unacceptable is that they don't integrate a warning in their software eg. Logitech Options, which should inform you to update the vulnerable FW on the unifying receiver.
First off i do not like the trend of giving every damn vulnerability found a cute name and logo.
Second, the tool presented here seems overly reliant on the presence of the Freedesktop permissions model.
Rather than having a tool that root can run to do the firmware update and leave it at that, there is talk of daemons and d-bus interfaces to schedule updates and whatsnot.
Maybe all this makes sense once one has 1000s of computers one wants to manage from a central UI. But for individual desktops it seems massively overdesigned.