Binary blob: Difference between revisions

Revision as of 20:21, 23 June 2006

Revision as of 22:34, 23 June 2006

Line 1:

In computer science, a '''binary blob''' is an opaque [[Binary file|binary]] object for which no source code is available. In some operating system communities, such as those of [[Ubuntu (Linux distribution)|Ubuntu]] and [[OpenBSD]], the term refers to partial or complete drivers provided by companies such as [[ATI Technologies|ATI]] and [[NVIDIA]] to provide support for their [[hardware]]. Such blobs can be a point of conflict between [[open source software|open source]] and [[free software]] advocates and developers and regular users of the operating system, as binary blobs can provide convenient support for popular hardware at the cost of the ability to read and modify every part of the operating system.

The OpenBSD project has a notable policy of not accepting 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<ref>{{cite web|last = 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|url = http://www.openbsd.org/lyrics.html#39|title = 3.9: "Blob!"|publisher = OpenBSD|accessdate = 2006-06-22}}</ref>. This stance is expected to be somewhat validated by information soon to be released revealing an exploit within the binary driver for a wireless network card.<ref>{{cite web|last = An article by Robert McMillan of IDG News Service regarding the hacking of a Wi-Fi binary blob driver - June 21, 2006|url = http://www.infoworld.com/article/06/06/21/79536_HNwifibreach_1.html|title = Researchers hack Wi-Fi driver to breach laptop|publisher = InfoWorld|accessdate = 2006-06-23}}</ref> Further details are expected at the [[August 2]] [[2006]] [[Black Hat Briefings|Black Hat USA]].

Others operating system projects, including [[NetBSD]], [[FreeBSD]], [[DragonFly BSD]], and the [[Ubuntu (Linux distribution)|Ubuntu]] and [[Fedora Core|Fedora]] [[Linux distributions]], take a pragmatic view and accept binary blobs as a fast route to the missing or enhanced functionality they provide. They include binary blobs for varied purposes, ranging from [[Redundant Array of Inexpensive Disks|RAID]], to networking and accelerated graphics drivers.

It is worth noting that the [[Free software foundation]] is actively campaigning against binary blobs, even though many [[Linux distributions]] include them.

A binary blob is not the same as a firmware package that accompanies a particular device. Firmware is the operating software required by the device's onboard microcontroller. Normally, it is stored in [[Flash memory|Flash EPROM]], but some manufacturers use RAM based firmware stores for cost and upgradeability reasons. Firmware blobs are acceptable to OpenBSD as long as the manufacturers allow them to be freely redistributed with the operating system <ref>{{cite web | title = OpenBSD Works To Open Wireless Chipsets - November 2, 2004 |url = http://kerneltrap.org/node/4118 | accessdate = 2006-06-23}}</ref>.

==Notes and references==