Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

No law or regulation that I know of specifies binary format.


The regulations specify they should not be easily changed. Distributing source makes it easier to change.


The carl firmware at https://github.com/chunkeey/carl9170fw should put that argument to rest. That is Wifi firmware source code for the Wifi I currently use.

Easily changed likely means there's a physical knob somewhere that you could accidentially poke as a layperson.

Not that you get a three year CS education, figure out how your distribution packages dependencies, install the correct embedded toolchain (good luck), find out exactly which chip is in your device, fetch the proper firmware source code in the right version, build the thing, figure out how to flash the result onto the chip / read the Linux kernel sources to figure out the filename inside /lib/firmware. That's not easy.

Even if this entire process was packaged (it is--see <https://packages.debian.org/sid/firmware-linux-free>), it probably still doesn't count (or at least shouldn't count) as "easily" changed.


Also, ath9k as a company.

More libre fw:

https://jxself.org/git/?p=linux-libre-firmware.git;a=tree

People stop talking out of his ass.


Please note that the Debian firmware-linux-free package does not build carl9170fw from source. There is proper packaging (source package called carl9170fw, binary package will be firmware-carl9170) being worked on but it isn't completed yet:

https://bugs.debian.org/994625


Unless you provide source code that builds reproducibly, and a detached signature that your hardware checks.



Wasn't that law only introduced a few years ago?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: