This program is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more details. You should have received a copy of the GNU Affero General Public License along with this program. If not, see . */ header('Content-type: text/html; charset=utf-8'); ob_start(); include_once "../common/variables.php"; include_once "../common/functions.php"; ?> Answers to Frequently Asked Questions about libreboot

Answers to Frequently Asked Questions about libreboot

Over time, there have been many questions asked about libreboot. We have to answer them every time, so it makes sense to document them here instead. More questions and answers will be added here, as time goes by. Back to home page

Hardware compatibility

General questions

Freedom questions

Operating Systems

Hardware compatibility

What systems are compatible with libreboot? (#compatibility)

See ../docs/hcl/index.html.

Several supported systems are also available with libreboot pre-installed. Check the suppliers page for more information.

Back to top of page

Why is the latest Intel hardware unsupported in libreboot? (#intel)

It is extremely unlikely that any post-2008 Intel hardware will ever be supported in libreboot, due to severe security and freedom issues; so severe, that the libreboot project recommends avoiding all modern Intel hardware. If you have an Intel based system affected by the problems described below, then you should get rid of it as soon as possible. The main issues are as follows:

Intel Management Engine (ME) (#intelme)

The ME is a separate processor that exists in all Intel chipsets past the year ~2006. It provides remote access capabilities, independently from the running operating system, with full access to RAM, and full networking support. With a functioning ME, your system is left wide open for attack. It can also phone home to Intel. It also handles the TPM, AMT (Active Management Technology), Boot Guard and various DRM mechanisms. The ME also performs some basic hardware initialization and power management, on recent systems.

The ME firmware is cryptographically signed, which means that you cannot run a modified version of it. You also can't boot without it. On some older chipsets (ICH8 and ICH9), it's possible to remove the ME firmware and still have a functioning system, where the ME itself is permanently deactivated. For instance, libreboot supports several ICH9 based laptops (e.g. Libreboot X200 and Libreboot T400); see ../docs/hcl/gm45_remove_me.html. On later chipsets (basically anything produced since 2010), this is not possible.

All modern Intel systems built after around the year 2008/2009 (after ICH9) require this proprietary firmware, and will not boot without it (or will shut down after 30 minutes). Replacing it is impossible, unless you are Intel (only they have the private key, necessary for signing the firmware). The Management Engine is covered on a lot of websites (e.g. me.bios.io, smashthestack.org, the coreboot wiki, wikipedia, FSF blog) and a book titled Platform Embedded Security Technology Revealed (PESTR), published by Apress (ISBN 9781430265719).

The Management Engine processor is an ARC microcontroller. The firmware is based on ThreadX RTOS, which is an embedded operating system designed specifically for those chips. Manufacturers (not just Intel) can pay for a (proprietary) license providing access to the source code, but they are not allowed to share it with anyone. In other words, even if Intel wanted to release the source code for this blob, they could not do so. Even if they did, the ME firmware is cryptographically signed, where the signature is verified at boot time. If you try to use your own modified version of the ME firmware, it will be rejected by the ARC processor and your system will not boot. In other words, the ME firmware is tivoized.

The Management Engine is a giant backdoor, allowing full access to your entire system for malicious adversaries. You don't have any privacy at all on systems that have this. The libreboot project strongly recommends that you avoid it entirely, and this means avoiding all recent generations of Intel hardware.

Firmware Support Package (FSP) (#fsp)

On all recent Intel systems, coreboot support has revolved around integrating a blob (for each system) called the FSP (firmware support package), which handles all of the hardware initialization, including memory initialization. Reverse engineering and replacing this blob is almost impossible, due to how complex it is. Even for the most skilled developer, it would take years to replace. Intel distributes this blob to firmware developers, without source.

Since the FSP is responsible for the early hardware initialization, that means it also handles SMM (System Management Mode). This is a special mode that operates below the operating system level. It's possible that rootkits could be implemented there, which could perform a number of attacks on the user (the list is endless). Any Intel system that has the proprietary FSP blob cannot be trusted at all. In fact, several SMM rootkits have been demonstrated in the wild (use a search engine to find them).

CPU microcode updates (#microcode)

All modern x86 CPUs (from Intel and AMD) use what is called microcode. CPUs are extremely complex, and difficult to get right, so the circuitry is designed in a very generic way, where only basic instructions are handled in hardware. Most of the instruction set is implemented using microcode, which is low-level software running inside the CPU that can specify how the circuitry is to be used, for each instruction. The built-in microcode is part of the hardware, and read-only. Both the circuitry and the microcode can have bugs, which could cause reliability issues.

Microcode updates are proprietary blobs, uploaded to the CPU at boot time, which patches the built-in microcode and disables buggy parts of the CPU to improve reliability. In the past, these updates were handled by the operating system kernel, but on all recent systems it is the boot firmware that must perform this task. Coreboot does distribute microcode updates for Intel and AMD CPUs, but libreboot cannot, because the whole point of libreboot is to be 100% free software.

On some older Intel CPUs, it is possible to exclude the microcode updates and not have any reliability issues in practise. All current libreboot systems work without microcode updates (otherwise, they wouldn't be supported in libreboot). However, all modern Intel CPUs require the microcode updates, otherwise the system will not boot at all, or it will be extremely unstable (memory corruption, for example).

Intel CPU microcode updates are signed, which means that you could not even run a modified version, even if you had the source code. If you try to upload your own modified updates, the CPU will reject them. In other words, the microcode updates are tivoized.

Intel is uncooperative (#intelbastards)

For years, coreboot has been struggling against Intel. Intel has been shown to be extremely uncooperative in general. Many coreboot developers, and companies, have tried to get Intel to cooperate; namely, releasing source code for the firmware components. Even Google, which sells millions of chromebooks (coreboot pre-installed) have been unable to persuade them.

Even when Intel does cooperate, they still don't provide source code. They might provide limited information (datasheets) under strict corporate NDA (non-disclosure agreement), but even that is not guaranteed. Even ODMs and IBVs can't get source code from Intel, in most cases (they will just integrate the blobs that Intel provides).

Recent Intel graphics chipsets also require firmware blobs.

Intel is only going to get worse when it comes to user freedom. Libreboot has no support recent Intel platforms, precisely because of the problems described above. The only way to solve this is to get Intel to change their policies and to be more friendly to the free software community. Reverse engineering won't solve anything long-term, unfortunately, but we need to keep doing it anyway. Moving forward, Intel hardware is a non-option unless a radical change happens within Intel.

Basically, all Intel hardware from year 2010 and beyond will never be supported by libreboot. The libreboot project is actively ignoring all modern Intel hardware at this point, and focusing on alternative platforms.

Back to top of page

Will the Purism Librem laptops be supported? (#librem)

Probably not. There are several privacy, security and freedom issues with these laptops, due to the Intel chipsets that they use. See #intel. There are signed proprietary blobs which cannot be replaced (e.g. Intel Management Engine and CPU microcode updates). It uses the proprietary Intel FSP blob for the entire hardware initialization, which Intel won't provide the source code for. The Video BIOS (initialization firmware for the graphics hardware) is also proprietary.

It will likely take many years to replace even one of these blobs, let alone all of them. Some of them (ME firmware and microcode) can't even be replaced, which immediately disqualifies these laptops from being added to libreboot. Google engineers have tried for many years to get source code from Intel, and to reverse engineer the blobs that Intel provides. So far, they have been unsuccessful. Google is also one of the companies that funds the coreboot project, and they hire a lot of the core developers, so it's not like they don't have vast resources at their disposal. Smaller companies have no chance.

It's a shame, because these laptops would be perfect for libreboot.

Back to top of page

Will the latest ThinkPad models be supported? (#thinkpads)

The latest ThinkPad generation supported in libreboot are the ones using the GM45 (ICH9) chipsets, such as the ThinkPad X200 or T400. ThinkPads newer than this generation will probably never be supported in libreboot, due to the fact that there are signed blobs that cannot be removed or replaced (e.g. Intel Management Engine). See #intel. Newer Lenovo laptops are also starting to use the Intel Boot Guard, which specifically blocks the use of firmware that has not been signed by the OEM.

Coreboot does have support for some more recent Lenovo laptops, but libreboot cannot support most of these.

Back to top of page

Will desktop/server hardware be supported? (#desktops)

A common issue with desktop hardware is the Video BIOS. Libreboot has to initialize the graphics chipset, but most graphics cards lack a free Video BIOS for this purpose. Some desktop motherboards supported in coreboot do have onboard graphics chipsets, but these also require a proprietary Video BIOS, in most cases.

There is the XGI Z9s PCI-E graphics card, documented under Board Ports in ../docs/tasks.html, which might be viable for you.

Although not desktop hardware (it's a server board), libreboot does support the ASUS KFSN4-DRE, with more server hardware support on the horizon, as outlined in ../docs/tasks.html. These boards have onboard graphics chipsets for which free native graphics initialization code does exist (as well as free initialization code for everything else in the boot firmware). These systems can be used to build very high-powered workstations, though it will be quite a bit bigger (physically) and more expensive than a standard desktop computer. However, it is the best option currently available in libreboot for this purpose.

Back to top of page

Hi, I have <insert random system here>, is it supported? (#randomhardware)

Most likely not. First, you must consult coreboot's own hardware compatibility list at http://www.coreboot.org/Supported_Motherboards and, if it is supported, check whether it can run without any proprietary blobs in the ROM image. If it can: wonderful! Libreboot can support it, and you can add support for it using the notes at ../docs/maintain/index.html. If not, then you will need to figure out how to reverse engineer and replace (or remove) those blobs that do still exist, in such a way where the system is still usable in some defined way.

For those systems where no coreboot support exists, you must first port it to coreboot and, if it can then run without any blobs in the ROM image, it can be added to libreboot. See: Motherboard Porting Guide (this is just the tip of the iceberg!)

Please note that board development should be done upstream (in coreboot) and merged downstream (into libreboot). This is the correct way to do it, and it is how the libreboot project is coordinated so as to avoid too much forking of the coreboot source code.

Back to top of page

What about ARM? (#arm)

TODO

Back to top of page

What about AMD? (#amd)

Libreboot has support for some AMD platforms, with more on the horizon. See ../docs/hcl/index.html.

More AMD-related information will be added to this page at a later date.

Back to top of page

General questions

How do I install libreboot? (#install)

See ../docs/install/index.html

Back to top of page

How do I program an SPI flash chip with the Raspberry Pi? (#repugnantpi)

The RPi can be used to install libreboot onto a system that uses SPI flash, but libreboot intentionally doesn't document it. Why? Blobs. The RPi requires a blob for the integrated video chipset, in order to boot. This was true of the original RPi, and has continued to be true for all subsequent revisions of the hardware. The RPi people clearly don't give a damn about your freedom, so we don't give a damn about endorsing them.

There are other, more freedom-friendly SPI programmers available, documented on ../docs/install/index.html.

Back to top of page

How do I set a boot password? (#bootpassword)

If you are using the GRUB payload, you can add a username and password (salted, hashed) to your GRUB configuration that resides inside the flash chip. The following guides (which also cover full disk encryption, including the /boot/ directory) show how to set a boot password in GRUB: ../docs/gnulinux/encrypted_trisquel.html and ../docs/gnulinux/encrypted_parabola.html

Back to top of page

How do I write-protect the flash chip? (#writeprotect)

By default, there is no write-protection on a libreboot system. This is for usability reasons, because most people do not have easy access to an external programmer for re-flashing their firmware, or they find it inconvenient to use an external programmer.

On some systems, it is possible to write-protect the firmware, such that it is rendered read-only at the OS level (external flashing is still possible, using dedicated hardware). For example, on current GM45 laptops (e.g. ThinkPad X200, T400), you can write-protect (see ../docs/hcl/gm45_remove_me.html#ich9gen). Depending on your flash chip, you can also write-protect the i945 laptops, such as the ThinkPad X60 or T60 (see ../docs/security/x60_security.html) and ../docs/security/t60_security.html for links to a video explaining it).

It's possible to write-protect on all libreboot systems, but the instructions need to be written. The documentation is in the main git repository, so you are welcome to submit patches adding these instructions.

Back to top of page

How do I change the BIOS settings? (#biossettings)

Libreboot actually uses the GRUB payload. More information about payloads can be found at coreboot.org/Payloads.

Libreboot inherits the modular payload concept from coreboot, which means that pre-OS bare-metal BIOS setup programs are not very practical. Coreboot (and libreboot) does include a utility called nvramtool, which can be used to change some settings. You can find nvramtool under coreboot/util/nvramtool/, in the libreboot source archives.

The -a option in nvramtool will list the available options, and -w can be used to change them. Consult the nvramtool documentation on the coreboot wiki for more information.

In practise, you don't need to change any of those settings, in most cases.

Back to top of page

Do I need to install a bootloader when installing GNU/Linux? (#bootloader)

Libreboot integrates the GRUB bootloader already, as a payload. This means that the GRUB bootloader is actually flashed, as part of the boot firmware (libreboot). This means that you do not have to install a boot loader on the HDD or SSD, when installing GNU/Linux. You'll be able to boot GNU/Linux just fine, using the bootloader (GRUB) that is in the flash chip.

This also means that even if you remove the HDD or SSD, you'll still have a functioning bootloader installed which could be used to boot a live GNU/Linux distribution installer from a USB flash drive. See .../docs/gnulinux/grub_boot_installer.html

Back to top of page

Do I need to re-flash when I re-install GNU/Linux? (#reinstallos)

Not anymore. Recent versions of libreboot (using the GRUB payload) will automatically switch to a GRUB configuration on the HDD or SSD, if it exists. You can also load a different GRUB configuration, from any kind of device that is supported in GRUB (such as a USB flash drive). For more information, see ../docs/gnulinux/grub_cbfs.html

Back to top of page

Freedom questions

What other firmware exists outside of libreboot? (#otherfirmware)

The main freedom issue on any system, is the boot firmware (usually referred to as a BIOS or UEFI). Libreboot replaces the boot firmware with fully free code, but even with libreboot, there may still be other hardware components in the system (e.g. laptop) that run their own dedicated firmware, sometimes proprietary. These are on secondary processors, where the firmware is usually read-only, written for very specific tasks. While these are unrelated to libreboot, technically speaking, it makes sense to document some of the issues here.

Note that these issues are not unique to libreboot systems. They apply universally, to most systems. The issues described below are the most common (or otherwise critical).

Dealing with these problems will most likely be handled by a separate project.

EC (embedded controller) firmware (#firmware-ec)

Most (all?) laptops have this. The EC (embedded controller) is a small, separate processor that basically processes inputs/outputs that are specific to laptops. For example:

Alexander Couzens from coreboot (lynxis on coreboot IRC) is working on a free EC firmware replacement for the ThinkPads that are supported in libreboot. See: https://github.com/lynxis/h8s-ec (not ready yet).

Most (all?) chromebooks have free EC firmware. Libreboot is currently looking into supporting a few ARM-based chromebooks.

EC is only present on laptops. On desktop/server boards it is absent (not required).

Back to top of page

HDD/SSD firmware (#firmware-hdd-ssd)

HDDs and SSDs have firmware in them, intended to handle the internal workings of the device while exposing a simple, standard interface (such as AHCI/SATA) that the OS software can use, generically. This firmware is transparent to the user of the drive.

HDDs and SSDs are quite complex, and these days contain quite complex hardware which is even capable of running an entire operating system (by this, we mean that the drive itself is actually running its own embedded operating system), even GNU/Linux or BusyBox/Linux.

Example attack that malicious firmware could do: substitute your SSH keys, allowing unauthorized remote access by an unknown adversary. Or maybe substitute your GPG keys. AHCI (SATA) drives also will have DMA, which means that they could read from system memory; the drive can have its own hidden storage, theoretically, where it could read your LUKS keys and store them unencrypted for future retrieval by an adversary.

With proper IOMMU, it might be possible to mitigate the DMA-related issues. USB drives (flash drive, HDD, etc) can be used, to avoid DMA.

Some proof of concepts have been demonstrated. For HDDs:
https://spritesmods.com/?art=hddhack&page=1
For SSDs:
http://www.bunniestudios.com/blog/?p=3554

Viable free replacement firmware is currently unknown to exist. For SSDs, the OpenSSD project may be interesting.

Back to top of page

NIC (ethernet controller) (#firmware-nic)

Ethernet NICs will typically run firmware inside, which is responsible for initializing the device internally. Theoretically, it could be configured to drop packets, or even modify them.

With proper IOMMU, it might be possible to mitigate the DMA-related issues. A USB NIC can also be used, which does not have DMA.

Back to top of page

CPU microcode (#firmware-cpu)

Implements an instruction set. See #microcode for a brief description. Here we mean microcode built in to the CPU. We are not talking about the updates supplied by the boot firmware (libreboot does not include microcode updates, and only supports systems that will work without it) Microcode can be very powerful. No proof that it's malicious, but it could theoretically

There isn't really a way to solve this, unless you use a CPU which does not have microcode. (ARM CPUs don't, but most ARM systems require blobs for the graphics hardware at present, and typically have other things like soldered wifi which might require blobs)

CPUs often on modern systems have a processor inside it for things like power management. ARM for example, has lots of these.

Back to top of page

Sound card (#firmware-sound)

Sound hardware (integrated or discrete) typically has firmware on it (DSP) for processing input/output. Again, a USB DAC is a good workaround.

Back to top of page

Web cam (#firmware-webcam

Webcams have firmware integrated into them that process the image input into the camera; adjusting focus, white balancing and so on. Can use USB webcam hardware, to work around potential DMA issues; integrated webcams (on laptops, for instance) are discouraged by the libreboot project.

Back to top of page

USB host controller (#firmware-usbhost)

Doesn't really apply to current libreboot systems (none of them have USB 3.0 at the moment), but USB 3.0 host controllers typically rely on firmware to implement the XHCI specification. Some newer coreboot ports also require this blob, if you want to use USB 3.0.

This doesn't affect libreboot at the moment, because all current systems that are supported only have older versions of USB available. USB devices also don't have DMA (but the USB host controller itself does).

With proper IOMMU, it might be possible to mitigate the DMA-related issues (with the host controller).

Back to top of page

WWAN firmware (#firmware-wwan)

Some laptops might have a simcard reader in them, with a card for handling WWAN, connecting to a 3g/4g (e.g. GSM) network. This is the same technology used in mobile phones, for remote network access (e.g. internet).

NOTE: not to be confused with wifi. Wifi is a different technology, and entirely unrelated.

The baseband processor inside the WWAN chip will have its own embedded operating system, most likely proprietary. Use of this technology also implies the same privacy issues as with mobile phones (remote tracking by the GSM network, by triangulating the signal).

On some laptops, these cards use USB (internally), so won't have DMA, but it's still a massive freedom and privacy issue. If you have an internal WWAN chip/card, the libreboot project recommends that you disable and (ideally, if possible) physically remove the hardware. If you absolutely must use this technology, an external USB dongle is much better because it can be easily removed when you don't need it, thereby disabling any external entities from tracking your location.

Use of ethernet or wifi is recommended, as opposed to mobile networks, as these are generally much safer.

On all current libreboot laptops, it is possible to remove the WWAN card and sim card if it exists. The WWAN card is next to the wifi card, and the sim card (if installed) will be in a slot underneath the battery, or next to the RAM.

Back to top of page

Operating Systems

Can I use GNU/Linux? (#gnulinux)

Absolutely! GNU/Linux is well-tested in libreboot, and highly recommended. See installing GNU/Linux and booting GNU/Linux.

Any recent distribution should work, as long as it uses KMS (kernel mode setting) for the graphics.

The Free Software Foundation maintains a list of free GNU/Linux distributions, certified to distribute and endorse free software, exclusively.

Back to top of page

Can I use GNU/Hurd? (#gnuhurd)

Unknown. Probably not. Feel free to try it, and report your findings.

GNU Hurd is a microkernel developed by the GNU project, and was (still is) intended to be the kernel for the GNU operating system. For historical reasons, Linux became the primarily adopted kernel (the libreboot project urges everyone to install and use linux-libre on their GNU systems), and was adapted for use with the GNU system. This is why we say GNU/Linux. Read the GNU/Linux FAQ.

Back to top of page

Can I use BSD? (#bsd)

Potentially. It may be possible to boot most BSD systems if you use the SeaBIOS payload. Most BSD systems seem to require a full Video BIOS implementation, which libreboot lacks for the most part, so you won't have a visual display, but you might be able to use an EHCI debug and/or serial console.

FreeBSD is rumoured to be somewhat compatible (with the GRUB payload, even), when booting with text-mode graphics initialization, but you probably won't be able to use X11.

For the most part, BSD systems remain untested in libreboot. BSD systems contain blobs, so do beware.

Back to top of page

Can I use Windows? (#windows)

Windows is incompatible with libreboot, and will probably remain so. Never use Windows.

Back to top of page

Are other operating systems compatible? (#otheros)

Unknown. Probably not.

Back to top of page