Original author(s) | Linus Torvalds et al. |
---|---|
Developer(s) | Free Software Foundation Latin America |
Initial release | February 20, 2008[1] |
Stable release | 6.9.4-gnu[2]
/ 12 June 2024 |
Repository | |
Written in | C and Assembly |
Platform | x86-64, i386, IA-32, ARM (Parabola), MIPS (Debian), m68k,[3] RISC-V,[4] IBM POWER8 and above[5] |
Available in | English |
Type | Kernel |
License | GPL-2.0-only[6] |
Website | www |
According to the Free Software Foundation Latin America, Linux-libre is a modified version of the Linux kernel that contains no binary blobs, obfuscated code, or code released under proprietary licenses.[7] In the Linux kernel, they are mostly used for proprietary firmware images. While generally redistributable, binary blobs do not give the user the freedom to audit, modify, or, consequently, redistribute their modified versions. The GNU Project keeps Linux-libre in synchronization with the mainline Linux kernel.[8]
The Linux kernel started to include binary blobs in 1996.[9] The work to clear out the binary blobs began in 2006 with gNewSense's find-firmware and gen-kernel. This work was taken further by the BLAG Linux distribution in 2007 when deblob and Linux-libre was born.[10][11]
Linux-libre was first released by the Free Software Foundation Latin America (FSFLA), then endorsed by the Free Software Foundation (FSF)[12] as a valuable component for the totally free Linux distributions. It became a GNU package in March 2012.[13] Alexandre Oliva is the project maintainer.
The removal process is achieved by using a script called deblob-main.[14] This script is inspired by the one used for gNewSense. Jeff Moe made subsequent modifications to meet certain requirements for its use with the BLAG Linux and GNU distribution. There is another script called deblob-check,[15] which is used to check if a kernel source file, a patch or a compressed sources file still contains software which is suspected of being proprietary.
Aside from the primary intended effect of running a system with only free software, the practical consequences of removing device firmware that a user is not allowed to study or modify has both positive and negative effects.
Removal of device firmware can be considered an advantage for security and stability.
When the firmware cannot be audited for bugs, security problems, and malicious functions such as backdoors, or when the firmware cannot be fixed by the Linux kernel maintainers themselves, even if they know of problems, it is possible for the entire system to be compromised by a malicious firmware. Without the ability to perform a security audit on manufacturer-provided firmware, even an innocent bug could undermine the safety of the running system.[16]
Removing proprietary firmware from the kernel will cause loss of functionality of certain hardware that does not have a free software replacement available.[8] This affects certain sound, video, TV tuner, and network cards, especially in the case of recent Intel Wi-Fi cards and recent nVidia graphics cards, as well as some other devices. When possible, free software replacement firmware is provided as a substitute,[8][17] such as the openfwwf[18] for b43, carl9170[19] and ath9k_htc[20] wireless card drivers. Reviewer Ramces Red summarized the issue with Linux-Libre, writing, "it does not always have the best hardware support."[8]
Linux-libre does not suggest the user install CPU microcode update bundles, since the code is proprietary.[21] Microcode update bundles have been used in the Linux kernel version, among other things, to mitigate hardware vulnerabilities.[22]
The source code and precompiled packages of the deblobbed Linux kernel are available directly from the distributions which use the Linux-libre scripts. Freed-ora is a subproject which prepares and maintains RPM packages based on Fedora.[23] There are also precompiled packages for Debian[24] and derived distributions such as Ubuntu.[25]
Considered small distributions
Historical
These distros do not use the packaged Linux-libre but instead completely remove binary blobs from the mainline Linux kernel. The source is then compiled and the resulting free Linux kernel is used by default in these systems:
Historical
Distributions in which Linux is the default kernel used and which propose Linux-libre as an alternative kernel: