Template:Otheruses4 In open source culture, binary blob is a pejorative term for an object file loaded into the kernel of a free or open source operating system without publicly available source code. The term is not usually applied to code running outside the kernel, for example BIOS code, firmware images, or userland programs.

When computer hardware vendors provide complete technical documentation for their products, operating system developers are able to write hardware device drivers to be included in the operating system kernels. However, some vendors, such as NVIDIA, do not provide complete documentation for some of their products and instead provide binary-only drivers (binary blobs); this practice is most common for accelerated graphics drivers, networking devices and RAID controllers.


When they can neither get hardware documentation nor device driver source code from a hardware vendor, some operating system projects, including NetBSD, FreeBSD, DragonFly BSD, and some GNU/Linux distributions, accept binary blobs as a fast route to the missing or enhanced functionality these blobs provide.[1]

The OpenBSD project has a notable policy of not accepting any binary blobs into its source tree, citing not only the potential for undetectable or irreparable security flaws but also its encroachment onto the openness and freedom of their software.[2]

Among GNU/Linux distributions, the gNewSense distribution is the most known for being actively against binary blobs. The Free Software Foundation (FSF) is actively campaigning against binary blobs and recommends gNewSense.[3]

Use via wrappersEdit

In order to make use of binary blob drivers available for other operating systems, some projects include software wrappers: examples include NdisWrapper for Linux and Project Evil for FreeBSD and NetBSD, both of which implement Microsoft's NDIS API to allow drivers written for Microsoft Windows to be used.


There are a number of reasons why binary blobs can cause problems: users cannot modify the software and distribute modified versions; blobs are unportable and typically limited to a few hardware architectures; the correctness of the driver code cannot be checked; the code cannot be audited for security by users or third parties; users are forced to trust vendors not to put backdoors and spyware into the blob; in case of bugs or vulnerabilities, the driver cannot be repaired by operating system developers; and the hardware vendor can decide not to support some operating systems or to abandon driver maintenance at any time.[4]

According to Microsoft, 28% of all crashes of their Vista operating system in 2007 were due to bugs in the binary blob drivers for Nvidia graphics cards.[5]


Firmware, the operating software required by a device's onboard microcontroller that accompanies some hardware, is generally not considered to be a binary blob. However, the FSF has begun campaigning for free BIOS firmware.[6] Often firmware is stored in onboard flash memory, but to decrease costs and ease upgrading, some manufacturers now use external firmware uploaded by the operating system. Although the firmware is present in the operating system, it is merely copied to the device and not executed by the CPU, lessening concerns about hidden security flaws. The OpenBSD project accepts binary firmware images and will redistribute the images if the licence permits.[7]

See also Edit


References Edit


External links Edit

Template:FOSSpt:Binary blob ru:Блоб

Cite error: <ref> tags exist, but no <references/> tag was found
Community content is available under CC-BY-SA unless otherwise noted.