Proprietary firmware

Print Print
Reading time 5:28

Proprietary firmware is any firmware on which the producer has set restrictions on use, private modification, copying, or republishing.

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.

Proprietary firmware may range from just a few kilobytes of microcode for a network interface controller[1] to megabytes of binaries for a wireless router. 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.

Difficult to avoid

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.[2]: One potential solution is going with open-source hardware, which goes a step further by also providing schematics for replicating the hardware itself.

Even though both proprietary firmware and proprietary device drivers are shipped in binary form,[3]: to be practical,[3]: the branding "binary blobs" is used only for the binary drivers.[4]:

Distribution issues

Many open-source operating systems reluctantly have to include proprietary firmware files in their distributions simply to make their device drivers work,[3] 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.[5] However, in order to do so, the operating system still has to have distribution rights for this proprietary microcode.[5] If such distributions rights are not obtained, then the device will not work; this especially presents a chicken-and-egg issue with wireless network interface controllers from certain manufacturers which cannot be used until such files are somehow obtained first, which is difficult to accomplish when the wireless card doesn't work.[5][2]:[6][7][1][8]

Security concerns

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. Theo de Raadt of OpenBSD suggests that wireless firmware are kept proprietary because of poor design quality, as well as firmware defects.[6][7]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".[9]

However, the security and quality/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.[3]


  • Breathalysers[10]
  • Most BIOS found in IBM-compatible Personal Computers[9]
  • 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


  1. ^ a b "/sys/dev/microcode/". OpenBSD.
  2. ^ a b Jeremy Andrews (2005-03-08). "Feature: OpenBSD's "Out of the Box" Wireless Support". KernelTrap. Archived from the original on 2005-03-09.
  3. ^ a b c d Jeremy Andrews (2006-05-02). "Interview: Theo de Raadt". KernelTrap. Archived from the original on 2006-06-03.
  4. ^ Jeremy Andrews (2006-04-19). "Interview: Jonathan Gray and Damien Bergamini". KernelTrap. Archived from the original on 2006-04-24. Firmwares are not considered blobs and can be shipped with the base system (provided their license allows free redistribution). Firmwares execute on the device itself, meaning they are not tied to a particular OS, while blobs execute on the host CPU, most of the time inside the kernel.
  5. ^ a b c Jeremy Andrews (2004-11-02). "Feature: OpenBSD Works To Open Wireless Chipsets". KernelTrap. Archived from the original on 2006-06-20.
  6. ^ a b 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.
  7. ^ a b Constantine A. Murenin (2006-12-10). "Почему так важно иметь документацию по программированию железа". (in Russian).
  8. ^ "sysutils/firmware". OpenBSD ports.
  9. ^ a b Mark Shuttleworth (2014-03-17). "ACPI, firmware and your security".
  10. ^ "Drunk drivers granted access to breathalyser source code". 2005-11-03.

Edited: 2021-06-18 15:09:57