Jump to content

Binary blob: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
Mac (talk | contribs)
23,294 edits
It's more a legal than technical term
Line 1: Line 1:
{{otheruses4|drivers|the database data type|binary large object}}
{{otheruses4|drivers|the database data type|binary large object}}
In [[computing]], a '''binary blob''' is an [[Objective Code|object file]] [[Linker|loaded]] into the [[Kernel (computer science)|kernel]] of a [[free software|free]] or [[open-source software|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 (computing)|userland]] programs.
In [[]], '''binary blob''' is an [[Objective Code|object file]] [[Linker|loaded]] into the [[Kernel (computer science)|kernel]] of a [[free software|free]] or [[open-source software|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 (computing)|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 [[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.

Revision as of 01:26, 3 June 2008

This article is about drivers. For the database data type, see binary large object.

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.

Acceptance

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 wrappers

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.

Problems

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]

During the August 2, 2006 Black Hat USA convention, an exploit within the binary driver for the Atheros wireless network cards used in MacBook Pros and elsewhere was claimed,[5] although it was later revealed that the exploit used third-party hardware and drivers.[6]

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.[7]

Firmware

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.[8] 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.[9]

See also

References

  1. ^ Matzan, Jem (15 June 2005). "BSD cognoscenti on Linux". NewsForge. Retrieved 2006-07-07. {{cite web}}: Check date values in: |date= (help) See Christos Zoulas's response to "Is sharing between Free/Open/NetBSD and the Linux kernel a common occurrence? And if so, does it go both ways?"
  2. ^ Music composed by Ty Semaka and Jonathan Lewis. Recorded, mixed and mastered by Jonathan Lewis of Moxam Studios (1-403-233-0350). Vocals and Lyrics by Ty Semaka & Theo de Raadt. Bass guitar, organ and bubbles by Jonathan Lewis. Guitar by Tom Bagley. Drums by Jim Buick. "3.9: "Blob!"". OpenBSD. Retrieved 2006-06-22.{{cite web}}: CS1 maint: multiple names: authors list (link) CS1 maint: numeric names: authors list (link)
  3. ^ "Protest against ATI nearly led to the arrest of RMS". Free Software Foundation. 27 April 2006. Retrieved 2006-10-10. {{cite web}}: Check date values in: |date= (help)
  4. ^ Andrews, Jeremy (April 19, 2006). "Interview with Jonathan Gray and Damien Bergamini". kerneltrap.org. Retrieved 2008-01-06.
  5. ^ Martin, Kelly (August 3 2006). "WiFi makes waves at Blackhat". SecurityFocus. Retrieved 2006-08-25. {{cite web}}: Check date values in: |date= (help)
  6. ^ Dalrymple, Jim (August 17 2006). "MacBook Wi-Fi hack didn't use Apple drivers". {{cite web}}: Check date values in: |date= (help)
  7. ^ "Vista-capable lawsuit paints picture of buggy NVIDIA drivers". Ars technica.
  8. ^ "Campaign for Free BIOS". Free Software Foundation. 2006-11-29. Retrieved 2007-01-02.
  9. ^ "OpenBSD Works To Open Wireless Chipsets". KernelTrap. November 2 2004. Retrieved 2006-06-23. {{cite web}}: Check date values in: |date= (help)
Retrieved from "https://en.wikipedia.org/w/index.php?title=Binary_blob&oldid=216752858"