Open-source Hardware

From Kicksecure
Jump to navigation Jump to search

Establishing Hardware Trust, Open-source Hardware Alternatives

Introduction[edit]

Info This chapter contains general security advice and is unspecific to Kicksecure. Readers interested in this topic should undertake significant research before purchasing any open-source hardware. It is also recommended to learn more about free hardware designsarchive.org.

Hardware Trust in Modern Computing[edit]

Security researcher and Qubes founder, Joanna Rutkowska, has noted that modern computing and networking security relies upon a critical foundation - trusted hardware and firmware domains. Even high-security operating systems have an security upper bound, since that is defined by the trustworthiness of hardware components that are ideally placed to compromise the entire system if bugs or backdoors are present: [1]

... for years we have been, similarly, assuming the underlying hardware, together with all the firmware that runs on it, such as the BIOS/UEFI and the SMM, GPU/NIC/SATA/HDD/EC firmware, etc., is all. . . trusted.


But isn’t that a rational assumption, after all?

Well, not quite: today we know it is rather unwise to assume all hardware and firmware is trusted. Various research from the last ten years, as discussed below, has provided enough evidence for that, in the author’s opinion. We should thus revisit this assumption. And given what’s at stake, the sooner we do this, the better.

Rutkowska has concluded the following hardware components and mechanisms are all vulnerable to exploitation and often flawed in their implementation, making them easy to "backdoor": [1]

  • x86 boot security (BIOS implementation).
  • Vt-d (CPU-enforced sandboxing of networking).
  • Graphics cards (GPUs) and sub-systems.
  • USB controllers.
  • Disk controllers (SATA etc.).
  • Embedded controllers (for keyboard operation, battery charging etc.).
  • Audio cards.
  • Peripheral devices.
  • Intel Management Engine (ME) and AMD Security Processor (embedded microcontrollers).
  • Built-in speakers, microphones and cameras.

This is particularly true for privileged, out-of-band hardware components like Intel ME's AMT which can read or write any of the host computer's memory, without any constraints - the perfect, undetectable rootkiting infrastructure. [1] In short, it appears that modern computing architectures are impossible to secure properly, especially since popular, proprietary hardware options (Intel and AMD) dominate the market. [2]

Open Source BIOS and Firmware Security Impact[edit]

Quote Kicksecure developer Patrick Schleizer [3]:

Hardware is solidified software.

Attempts on getting BIOS, Intel ME, AMD PSP are awesome, an important step but all just scratching the surface. The following video elaborates on that.

Disclaimer: I didn’t look much into RISC-V. This isn’t an endorsement / non-endorsement of RISC-V. That video isn’t much of a RISC-V promotion. The video is chosen as an example because it nicely elaborates on the extremely difficulty of having hardware that is secure, reasonable certain free of backdoors, Open Hardware, and whatnot.

https://www.youtube.com/watch?v=zXwy65d_tu8archive.org

Freedom? Security? The hardware is proprietary. In simplified terms, there is no meaningful distinction between hardware and security from a freedom and security perspective. Maybe the term “hardware acceleration” easily illustrates that. Hardware in a sense is solidified software. Hardware is for a large part just a different representation of software. What’s software? One level to look at it, it’s just zero’s and one’s on some storage medium. What hardware does is has concepts how to process incoming data / electricity burnt, solidified into silicon. You need a complex program to write a complex blueprint which then creates other complex files which then are used by complex machines which then create the actual hardware. At each step, a backdoor could be introduced.

See also this presentation 36C3 - Open Source is Insufficient to Solve Trust Problems in Hardwarearchive.org by Andrew "bunnie" Huang or BlueHat IL 2019 - Andrew "bunnie" Huang - Supply Chain Security: "If I were a Nation State...”archive.org.

A CPU is not just a dumb piece of hardware that can do basic calculations at high speed. Modern CPU from Intel / AMD have many "software alike" features built-in. To name a few of a plethora of examples:

  • Hardware accelerated AES encryption, the AES instruction setarchive.org. Historically AES encryption was implemented as software. Nowadays implementations of AES are implemented as hardware.
  • Hardware virtualizationarchive.org such as Intel VT-xarchive.org or AMD-Varchive.org are complex CPU instructions directly built into the CPU.
  • RDRANDarchive.org, quote Wikipedia "is an instruction for returning random numbers from an Intel on-chip hardware random number generator which has been seeded by an on-chip entropy source."

See also these blog posts by Joanna Rutkowska, founder of Qubes OS:

For a video showing that hardware based encryption (in a different context) can be vulnerable, see this computer chaos club (CCC) talk 35C3 - Self-encrypting deceptionarchive.org

https://en.m.wikipedia.org/wiki/EFusearchive.org

Open-source Hardware Alternatives[edit]

People who are motivated to avoid proprietary hardware solutions are in a bind. There are few options available that are truly "free" (as in freedom), affordable and which provide suitable processing power to run "secure" operating systems like Kicksecure for Qubes, because specific hardware requirements like VT-d and VT-x are necessary for compatibility with future software releases.

Open-source hardware is also not perfectly secure since it is not "stateless". Meeting this standard requires there be no persistent storage at all. [1] Further, "free" hardware does not really exist, since by definition it requires that hardware is free at all levels, including: licensing, the chip and circuit board designs, the field-programmable gate array, source code, relevant repositories and so on. Also, proprietary "soft cores" which are often incorporated in various hardware circuits need to be purged to meet the necessary criteria. [4] [5]

ARM-based Platforms[edit]

ARM architecture dominates smartphone and tablet markets, providing a good level of performance. However, an open-source "ARM processor" is non-existent, because only the specifications and other intellectual property (IP) are released to manufacturers under specific licenses. This leads to NVIDIA, Samsung and others combining the ARM IP with their own, leading to the actual, customized processors called System-on-Chips (SoCs). [1] ARM SoCs also often have a TrustZone extension, with implementation providing similar functionality to Intel's ME. There is nothing special in ARM architecture that prevents the possible introduction of backdoors.

Open-source Processors[edit]

Unfortunately, a fully open-source, Linux-capable based processor (SoC)archive.org is not yet available, with the design still being finalized. While this project will eventually allow a 64-bit RISC-V instruction set architecture (ISA) and the development of low-cost boards, the wait may be lengthy (many years) and it is not clear such processors will perform well enough for typical desktop workflows like watching movies, running browsers, using office suites and so on. It is also unknown whether this design will allow for security technologies like IOMMU and memory virtualization. [6] [1]

Another initiative related to this topic is the OpenPOWER Foundationarchive.org, which was established in 2013. The foundation has a number of influential partners, including IBM, Google, NVIDIA, Samsung Electronics and Canonical. Critically, IBM is "...opening up technology surrounding their Power Architecture offerings, such as processor specifications, firmware and software with a liberal license, and will be using a collaborative development model with their partners." [7] [8] The initiative will also include opensource software, firmware, the KVM hypervisor and a little endian Linux operating system. [9] OpenPOWER code can be found on GitHubarchive.org.

Final Hardware Purchase[edit]

The Free Software Foundation (FSF) makes a number of relevant recommendations: [10]

  • Find devices which support fully free distributions of GNU/Linux.
  • Purchase hardware:
    • From manufacturers who support GNU/Linux.
    • Which supports coreboot/libreboot as a proprietary BIOS replacement.
    • Without the need for proprietary drivers or firmware; see hdnode.orgarchive.org.
  • Check the FSF criteriaarchive.org for hardware certification requirements.
  • If looking for a single-board computer (SBC), check the listarchive.org of available (flawed) hardware. [11]
  • Check the list of motherboardsarchive.org that are compatible with coreboot. [12]

A list of suppliers selling or providing Librebootarchive.org pre-installed on laptops, desktops, servers and motherboards can be found herearchive.org. Readers interested in purchasing hardware with Coreboot pre-installed can start their search herearchive.org.

Buyer Considerations[edit]

Based on the preceding information and links, those seeking an open-source solution need to make a compromise. Since an open source LowRISC processor based on the RISC-V ISA -- which can support a fully-fledged operating system -- does not yet exist, [13] the closest thing available is single-board computers (SBCs)archive.org, which are delivered as one circuit board that are powerful enough to run a real operating system. These systems generally contain a SoC with an ARM processor, with options like Novenaarchive.org and PandaBoardESarchive.org falling into this category. However, they still have a number of closed-source binary blobs and the FSF also notes "severe flaws" in these products due to proprietary design concerns.

Purismarchive.org also seek to remove as many proprietary blobs as possible, for example by using coreboot in place of the standard BIOS implementation. Unfortunately, this solution is expensive and still relies on an Intel processor. Despite the claims that ME is "neutralized", the ME still poses potential security threats to the user as highlighted in Rutkowska's research.

The following options may be suitable, depending on user requirements:

  • Low-end computers: Check this listarchive.org from the FSF, as they are certified "RYF" (Respects Your Freedom hardware product certification).
  • High-end computers: Options like VKGS-WORK-D16archive.org are compatible with Coreboot/Libreboot BIOS and are capable of booting Qubes OS. It also has no proprietary software or firmware blobs.
  • Worthy mention: Raptor Computing Systemsarchive.org have built their processors based on IBM OpenPOWER technology.

In the coming years when open-source processors and hardware designs further mature and the necessary functionality is provided for virtualization, reasonable and fairly-priced alternatives to proprietary architectures will start to emerge.

Firmware Considerations[edit]

Open-source hardwarearchive.org is not affected by the non-free firmware updates issue described in the previous chapter. Such hardware might be more trustworthy, but open-source firmware can be just as insecure as a proprietary one. Fortunately, open source firmware increases the chances of actually making it secure, with options like coreboot appearing to be a promising solution. [1]

See Also[edit]

References[edit]

  1. ↑ 1.0 1.1 1.2 1.3 1.4 1.5 1.6 https://blog.invisiblethings.org/papers/2015/x86_harmful.pdfarchive.org
  2. ↑ AMD-based x86 platforms have analogous hardware mechanisms to Intel, so they are not theoretically safer.
  3. ↑ A login requirement was enabled by Qubes forum after this was posted: https://forum.qubes-os.org/t/intel-vs-arm-vs-power-vs-risc-v-architecture-freedom-perspective/14172/11
  4. ↑ https://www.wired.com/2015/03/richard-stallman-how-to-make-hardware-designs-free/archive.org
  5. ↑ https://www.wired.com/2015/03/need-free-digital-hardware-designs/archive.org
  6. ↑ https://lowrisc.org/about/archive.org
  7. ↑ https://en.wikipedia.org/wiki/OpenPOWER_Foundationarchive.org
  8. ↑ Primarily the Power8 chip technology, but previous designs will also be available for licensing.
  9. ↑ Firmware to boot Linux was released in 2014.
  10. ↑ https://www.fsf.org/resources/hwarchive.org
  11. ↑ None of these options are completely free in their design.
  12. ↑ Some motherboards still require proprietary CPU microcode.
  13. ↑ The LowRISC FAQarchive.org notes the rough processor speed that is expected:

    The clock rate achieved will depend on the technology node and particular process selected. As a rough guide we would expect ~0.5-1GHz at 40nm and ~1.0-1.5GHz at 28nm.
  14. ↑ For example, see the T2P9D01 Mainboard documentarchive.org.
  15. ↑ This requires:

    ... that information about the hardware is easily discerned so that others can make it – coupling it closely to the maker movement. Hardware design (i.e. mechanical drawings, schematics, bills of material, PCB layout data, HDL source code and integrated circuit layout data), in addition to the software that drives the hardware, are all released under free/libre terms.
  16. ↑ https://www.fsf.org/blogs/licensing/support-the-talos-ii-a-candidate-for-respects-your-freedom-certification-by-pre-ordering-by-september-15archive.org
  17. ↑ https://twitter.com/Whonix/status/1190634591045865472archive.org (nitterarchive.org)

Unfinished: This wiki is a work in progress. Please do not report broken links until this notice is removed, use Search Engines First and contribute improving this wiki.

Your support makes
all the difference!

We believe security software like Kicksecure needs to remain open source and independent. Would you help sustain and grow the project? Learn more about our 10 year success story and maybe DONATE!

Retrieved from "https://www.kicksecure.com/w/index.php?title=Open-source_Hardware&oldid=77276"