I'm not a fan of GrapheneOS, but the point they bring up here is valid. There is already proprietary firmware on your computer. There's no reason why you shouldn't be updating it to protect yourself from serious exploits. The FSF takes an ideological stance rather than a practical one, unfortunately.

[–] krolden@lemmy.ml 7 points 2 months ago (3 children)

Except they also advocate using compute devices that only use blobless firmware

[–] exu@feditown.com 8 points 2 months ago (1 children)

Yeah, the FSF stance on firmware is really weird.

Basically, if the firmware is not intended to be updated it's fine. But distributing updates, like security fixes, for firmware as blobs is somehow bad.

However, there is one exception for secondary embedded processors. The exception applies to software delivered inside auxiliary and low-level processors and FPGAs, within which software installation is not intended after the user obtains the product. This can include, for instance, microcode inside a processor, firmware built into an I/O device, or the gate pattern of an FPGA. The software in such secondary processors does not count as product software.

https://ryf.fsf.org/about/criteria

Here's an article from the previous time (?) this topic came up.

https://ariadne.space/2022/01/22/the-fsfs-relationship-with-firmware-is-harmful-to-free-software-users/

[–] dragnucs@lemmy.ml 1 points 2 months ago

Not really weired. For example, a keyboard has a firmware. 99% of keyboards have no way of it being updated or changed. It is part of its electronics. So not a big deal. But, if a keyboard has a way to update the firmware or install another one, then it should be FOSS.

load more comments (1 replies)

load more comments (3 replies)