Proprietary firmware

Proprietary firmware is any firmware that has had its use, private modification, copying, or republishing restricted by the producer. Proprietors may enforce restrictions by technical means, such as by restricting source code access, firmware replacement restrictions (by denying complete tooling that may be necessary in order to recompile and replace the firmware), or by legal means, such as through copyright and patents. Alternatives to proprietary firmware may be free (libre) or open-source.

Distribution

Main article: Proprietary device driver § Device firmware

Proprietary firmware (and especially the microcode) is much more difficult to avoid than proprietary software or even proprietary device drivers, because the firmware is usually very specific to the manufacturer of each device (often being unique for each model), and the programming documentation and complete specifications that would be necessary to create a replacement are often withheld by the hardware manufacturer.^[1]

Many open-source operating systems reluctantly choose to include proprietary firmware files in their distributions simply to make their device drivers work,^[2] because manufacturers try to save money by removing flash memory or EEPROM from their devices, requiring the operating system to upload the firmware each time the device is used.^[3] However, in order to do so, the operating system still has to have distribution rights for this proprietary microcode.^[3]

Security concerns

Main article: Firmware § Security risks

Proprietary firmware poses a significant security risk to the user because of the direct memory access (DMA) architecture of modern computers and the potential for DMA attacks.^{[citation needed]} Theo de Raadt of OpenBSD suggests that wireless firmware are kept proprietary because of poor design quality and firmware defects.^[4][5] Mark Shuttleworth of Ubuntu suggests that "it's reasonable to assume that all firmware is a cesspool of insecurity courtesy of incompetence of the worst degree from manufacturers, and competence of the highest degree from a very wide range of such agencies".^[6]

The security and reliability risks posed by proprietary microcode may be lower than those posed by proprietary device drivers, because the microcode in this context isn't linked against the operating system, and doesn't run on the host's main processor.^[2]

Alternatives

Custom firmware may still be available for certain products, which is often free and open-source software, and is especially popular in certain segments of hardware like gaming consoles, wireless routers and Android phones, which are capable of running complete general-purpose operating systems like Linux, FreeBSD or NetBSD, which are often the systems used by the manufacturer in their original proprietary firmware.

Another potential solution is going with open-source hardware, which goes a step further by also providing schematics for replicating the hardware itself.

Examples

• Breathalysers^[7]
• Most BIOS found in IBM-compatible Personal Computers^[6]
• Most UEFI found in modern x86 Computers
• ARCS, used in computers from Silicon Graphics
• Run-Time Abstraction Services (RTAS), used in computers from IBM
• The iPod's control menus
• Cisco IOS
• Microcode in wireless network interface controllers, video cards, x86 processors, etc.

See also

• ROM image
• Open-source hardware
• Coreboot
• Open Firmware

References

1. Jeremy Andrews (2005-03-08). "Feature: OpenBSD's "Out of the Box" Wireless Support". KernelTrap. Archived from the original on 2005-03-09.
2. Jeremy Andrews (2006-05-02). "Interview: Theo de Raadt". KernelTrap. Archived from the original on 2006-06-03.
3. Jeremy Andrews (2004-11-02). "Feature: OpenBSD Works To Open Wireless Chipsets". KernelTrap. Archived from the original on 2006-06-20.
4. Theo de Raadt (2016-12-03). "Page 13: The hardware: 802.11 wireless networking (more detail)". Open Documentation for Hardware. OpenCON 2006, 2–3 December 2006. Courtyard Venice Airport, Venice/Tessera, Italy.
5. Constantine A. Murenin (2006-12-10). "Почему так важно иметь документацию по программированию железа". Linux.org.ru (in Russian).
6. Mark Shuttleworth (2014-03-17). "ACPI, firmware and your security".
7. "Drunk drivers granted access to breathalyser source code". 2005-11-03. Archived from the original on 2008-09-30.