Hardware

Where Faraday runs, and what the build of each platform carries and leaves out. Every fact here is from Faraday's documents; each section names its source.

Supported hardware Platforms Screens and layout One build per platform The boards Left out Cameras and input Help test Considered

Supported hardware

One card for each piece of hardware the download page offers. Its page says what it needs, its screen and its builds.

The Pi's two setups

The Pi has one image. It finds the screen attached when it starts, so the same card runs either setup.

The 2.8-inch panel

  • A Raspberry Pi 3 Model B or B+
  • Waveshare 2.8inch DPI LCD
  • A microSD card of 256 MB or more, and a power supply
  • A USB webcam that offers uncompressed (YUYV) frames, or a Raspberry Pi Camera Module v1 or v2

An HDMI monitor

  • A Raspberry Pi 3 or Zero 2 W
  • An HDMI monitor with a USB keyboard and a mouse, or Waveshare's 10.1inch HDMI LCD (B) with its USB touch
  • A microSD card of 256 MB or more, and a power supply
  • A USB webcam that offers uncompressed (YUYV) frames, or a Raspberry Pi Camera Module v1 or v2

Download the Pi image

Platforms

Where Faraday runs, and the state of each.

PlatformRuns onState
The stickA 64-bit PC with UEFI firmware (one build, with efi=disable_early_pci_dma on its command line); Intel Macs plannedReleased; booted in QEMU with OVMF and on a laptop (the kernel with efi=disable_early_pci_dma, 2026-10-31)
The Pi, the 2.8-inch screenA Raspberry Pi 3B, 3B+ or Zero 2 W with the Waveshare 2.8-inch DPI panel, with USB keyboards, mice and sticksBuilt, not tried on the one image: looking for testers (the earlier 2.8-inch image was tried on the panel)
The Pi, HDMI screenA Raspberry Pi 3B, 3B+ or Zero 2 W with an HDMI monitor and a USB keyboard and mouse, or Waveshare's 10.1-inch HDMI LCD (B) with its USB touchBuilt, not tried: looking for testers
The Pi Zero 2 WA Raspberry Pi Zero 2 W with the same screensBuilt, not tried: the Pi image carries its device tree; nobody has booted it on a Zero 2 W
The Apple Silicon stickMacs with M1 or M2Planned: its Spec is docs/MAC.md
Faraday DemoLinux and Windows, x86_64Released, for trying Faraday: not air-gapped
The StarterLinux and Windows, x86_64; macOS specifiedReleased on Linux and Windows

The Starter writes sticks and Pi cards and holds no keys. Faraday Demo runs on a computer that is on a network. It is a simulator with Practice's samples, not a signing device.

How each is kept off the network

The stick and the Pi

The network stack is not compiled in: no Ethernet, Wi-Fi, Bluetooth or USB network driver, and no socket layer. A Pi 3's Wi-Fi and Bluetooth chip is never given its firmware, so it never runs. A PC's own disks are invisible.

Faraday Demo and the Starter

Faraday Demo and the Starter run on a computer that may be on a network. Neither is a place for real keys.

Screens and layout

Faraday lays every screen out again at its own size. Its size class comes from its width in dp at its density, divided by the text size: a larger text steps the layout down.

ClassWidthNavigationTypical screen
Compactunder 600 dpThe navigation bar at the footThe Pi panel (268 × 358), a narrow window, a 7-inch panel in portrait (565 × 964 at its 170 dpi)
Medium600 to 839 dpThe navigation railA half-screen window
Expanded840 to 1199 dpThe navigation railA 7-inch panel in landscape (964 × 565), a 10-inch panel in portrait (853 × 1365 at its 150 dpi), a small laptop window
Large1200 to 1599 dpThe expanded navigation railThe desktop app's default window (1280 × 800), a 10-inch panel in landscape
Extra-large1600 dp and overThe expanded navigation railA full monitor at 1×: 1920 × 1080, 2560 × 1440

Height counts where it is short. A screen under 480 dp tall is short, as the Pi's 2.8-inch panel is: there Home is the menu. One under 600 dp tall is low, as a 7-inch panel in landscape is. docs/LAYOUT.md says what each class lays out.

The layout each screen gets

ScreenPixelsDensitydpClass, navigation
Waveshare 2.8-inch DPI panel (the Pi)480 × 640, portrait natively286 dpi268 × 358Compact and short: Home is the menu, every other page has its bar with a back chevron; no Rotation
A 7-inch panel, landscape (a small tablet, a panel PC or a portable monitor on the stick)1024 × 600170 dpi, from its EDID964 × 565Expanded and low: the navigation rail
A 7-inch panel, portrait600 × 1024170 dpi565 × 964Compact: the navigation bar at the foot
A 10-inch panel, portrait800 × 1280150 dpi853 × 1365Expanded: the rail
A 10-inch panel, landscape1280 × 800150 dpi1365 × 853Large: the expanded rail
A PC monitor or laptop screen on the stickIts firmware modefaraday.dpi=160, doubled at 2800 pixels wide or moreIts pixels, or halfExpanded to extra-large: the rail or the expanded rail
An HDMI screen on the PiThe mode the kernel chose from its EDIDIts EDID's on a screen of 11 inches or less, faraday.dpi=160 otherwiseBy its modeBy its width, as on the stick
Faraday Demo's window1280 × 800 at first, any sizeThe system's scaleIts sizeAny class, laid out again at every size; the Size menu shows the panels above

A 7-inch or 10-inch panel starts in landscape, and Settings › Display › Rotation turns it and its touch. A screen of 11 inches or less takes its density from its EDID. The app lays out every one of these sizes. The Pi image is built for the 2.8-inch panel and for an HDMI screen, one image that finds its screen at boot: faraday/image/panels/any holds the two screens' values and overlays, and faraday/image/panels/ the PC's firmware framebuffer. A 7-inch screen is the stick's, on a small PC or tablet, or an HDMI one on the Pi.

Orientation

The layout follows the screen's width in each orientation: a 7-inch panel is expanded and low in landscape, with the rail, and compact in portrait, with the navigation bar at the foot. The Pi's 2.8-inch panel stays in portrait: it has no Rotation.

docs/ORIENTATION.md

Motion

Every platform starts with full motion. Reduce motion (Settings › Appearance) is off on a first start. Where frames are slow, the automatic gate turns fades off by itself: it does so when the steps are more than 55 ms apart, and brings them back after 24 fast frames in a row.

docs/MOTION.md

One build per platform

The PC stick is one image, and the Pi has one image for every screen. There is no build to choose between.

PlatformThe kernel
The PiDRM for HDMI and the 2.8-inch DPI panel; USB keyboards, mice and touchscreens; USB storage
The PC stickefi=disable_early_pci_dma on its built-in command line, so no PCI device the firmware left running can write to memory before the kernel has set up the IOMMU; kernel.cmdline makes the kernel check require it

The PC's kernel is the EFI program itself, with its root filesystem inside it and the firmware's framebuffer, so nothing it runs needs the devices that flag cuts off. KCMP is forbidden on the PC (its own kernel.forbidden) and allowed on the Pi, where DRM selects it.

What the PC stick carries

  • efi=disable_early_pci_dma on its built-in command line, and a kernel check that requires it.
  • The firmware's framebuffer for the screen, and the built-in keyboard, touchpad and touchscreen.
  • USB keyboards, mice, touchscreens and storage, under the approval rules below.

What the Pi carries

  • DRM for the display only: no GPU render node, no HDMI-CEC, no HDMI audio.
  • HDMI: the kernel reads a monitor's EDID.
  • USB keyboards, mice and touchscreens, under the PC stick's approval rules.
  • The screen's own USB touchscreen, named in the screen's profile, as trusted input.
  • USB storage, one partition at a time, read only while no secret is open, as on the PC.

Every build is safe in practice

The root filesystem, the app and its checks are the same on both platforms; the kernel and its command line are each board's own.

Each board has its own list of forbidden kernel options, and the build fails if one is on.

The boards compared

What starts before Faraday, and where it is kept, differs from board to board.

Raspberry Pi 3 and Zero 2 W

Everything they start from is on the card: the firmware, and the kernel with the system linked into it. A fresh card is a clean start.

The chip's one-time-programmable memory is out of the app's reach: its mailbox driver is not built. The Wi-Fi and Bluetooth chip is never given its firmware, so it never runs.

One card starts the 3B, 3B+ and Zero 2 W: it carries each board's device tree, and the firmware loads the one for the board it starts on. Nobody has started a Zero 2 W with it yet. The Zero 2 W has no DSI connector, so a screen on the DSI connector does not fit it.

Raspberry Pi 4 Planned

The Pi 4 starts from a boot loader kept in an EEPROM on the board, not on the card. A card carrying recovery.bin can rewrite it, so on a Pi 4 a fresh card is not a clean start. Its security is close to a PC's: its boot code is on the board. Its USB sits behind PCIe.

It will run the same images as the Pi 3: its 32-bit kernel, firmware and device tree beside the Pi 3's, the system the same. No Faraday card carries a boot loader update, and its kernel leaves out SPI_SPIDEV and SPI_BCM2835.

Before first use, restore Raspberry Pi's boot loader with Raspberry Pi Imager. A wire to test point TP5 locks the boot loader in hardware.

A laptop or PC

Its firmware runs before Faraday, and Faraday does not defend against compromised firmware. Nor against the management processors below the operating system, Intel's Management Engine and AMD's Platform Security Processor: What else runs on this computer says which computers have them and what to do.

Between the firmware and the kernel's IOMMU there is a window in which a PCI device the firmware left running could write to memory. The stick closes it: its kernel's built-in command line carries efi=disable_early_pci_dma, and its kernel check requires it. The stick has been tried on a laptop with it. The IOMMU is on from boot in strict mode.

Thunderbolt is left out. A Thunderbolt or USB4 port is a PCIe slot on the outside of the case; without the Thunderbolt driver it carries USB and DisplayPort and nothing that speaks PCIe. The computer's own SATA, NVMe and eMMC disks are invisible: their drivers are not built.

Raspberry Pi 5 Later

The Pi 5 comes after the Pi 4.

What every build leaves out

On the PC and the Pi. Each kernel is built with a fixed list of drivers.

  • No network stack. No Ethernet, Wi-Fi, Bluetooth or USB network driver, and no socket layer for one to use. A Pi's Wi-Fi and Bluetooth chip is never given its firmware.
  • No kernel modules. The drivers are built in, and kernel lockdown is forced to its strictest level from early boot.
  • No desktop. No X11, Wayland, window manager, GPU driver, toolkit or browser engine: one Rust program lays out every screen and writes its pixels.
  • No login. No getty, su, sudo or passwd, and root's password is locked. Every process that handles input runs as an unprivileged user.
  • Nothing written to the computer. No driver for its disk and no access to its firmware variables. The system runs from memory, and nothing is mounted from the boot medium after it starts.
  • No swap, suspend, hibernation or core dumps. Nothing in memory is paged out.
  • No logs. The release images write no boot report and no timings, and their kernel log stays closed to the app.
  • No new keyboard without the code. A keyboard other than the built-in one types nothing until it types a random code shown on the screen (below).

Cameras and input

Faraday reads QR codes through a camera, and files from sticks and cards.

The PC stickThe Pi
Touch, keyboard, pointerBuilt-in keyboard, touchpad and touchscreen; USB ones once approvedThe panel's touch, or the HDMI panel's USB touch once approved by a tap on the target; other USB keyboards, mice and touchscreens once approved, as on the stick
Camera, for QR codesA USB webcam, plugged in or built in, that offers uncompressed frames; not a MIPI cameraA USB webcam that offers uncompressed frames; a Camera Module v1 or v2, tried with the earlier 2.8-inch image, and on the one image beside the 2.8-inch panel and an HDMI screen to be tried; not Camera Module 3
FilesUSB sticks; an SD card only in a USB readerIts own SD slot and USB sticks

Cameras

A USB webcam that offers uncompressed frames (YUYV) works, plugged in or built in. A webcam that sends only MJPEG frames does not work yet.

On a Pi, the camera is a Raspberry Pi Camera Module v1 or v2 on the board's ribbon connector, or a USB webcam. Camera Module 3 is not supported. For a housing, a bare USB camera board with screw holes and an adjustable (M12) lens also fits well: screw it in place and set its focus once at the distance a QR code is held.

Not working yet: a MIPI camera. Most laptop webcams made after about 2020 are sensors on a MIPI lane behind an image processor, and Faraday carries neither their driver nor its firmware. Such a computer shows the scanner's file path and no viewfinder; a USB webcam in a port works. A webcam plugged in after the system starts is not picked up.

Touchscreens

On a PC: a built-in touchscreen, and a USB one once approved.

On the Pi: the panel's own touch, and USB touchscreens once approved; the one the screen's profile names, such as the 10-inch HDMI panel's, is trusted input and needs no approval.

Keyboards and pointers

A keyboard other than the computer's built-in one is ignored until it types a random code shown on the screen, and until it is unplugged if it types three codes' worth of letters without it. After three such keyboards, new ones are ignored until Faraday starts again.

A new pointer is ignored until a person approves it with trusted input. USB interfaces are authorised one at a time: a stick that also claims to be a keyboard types nothing.

Files

FAT only, read and written by Faraday's own disk process in Rust, not by the kernel. A partition holding anything else is left alone.

On a PC: USB sticks, and an SD card in a USB reader. On the Pi: its own card slot and USB sticks.

Help test

An image is published before it has been tried on its hardware, marked Looking for testers. Once it has been tried there, its screen's settings are confirmed and its page marks it Tested. The pages never say whose hardware it was tried on.

The dev image

Built from the source with dev=1, it shows the kernel's messages on the screen and writes faraday-boot-report.txt every 30 seconds: the kernel log, the screen and devices found, and no secret. Send that file, and the build ID (uname -r on its console), with the report. Never use the dev image for keys that matter.

DEVELOPING §6.2 says how to build it.

Considered, not supported

Boards studied. Faraday does not run on them yet.

Waveshare ESP32-P4-WIFI6-Touch-LCD-7B Under study

A 7-inch 1024 × 600 IPS board with GT911 capacitive touch, MIPI-DSI and MIPI-CSI. It has an ESP32-P4 (two RISC-V cores, up to 400 MHz, 768 KB SRAM, 32 MB PSRAM, 32 MB flash) and an ESP32-C6 module for Wi-Fi 6 and Bluetooth 5. It costs about US $50. Studied without a board on 2026-10-28. Not supported, and not being ported.

What stands in the way

  1. Vault memory. Faraday makes vaults of at least 64 MiB of Argon2 memory, and the board has 32 MB in all. A vault it could open would be made at 16 MiB or less, below Light. That is the owner's decision, not taken.

  2. The radio. The C6 boots its own flash at power-on, whatever the P4 runs. Without a radio means the C6 module desoldered, or its flash erased and the erase checked. No ESP32-P4 board without a C6 was found. ESP32-S3 boards carry the radio in the chip and are not candidates.

  3. The security model. docs/SECURITY-MODEL.md rests on Linux:

    • separate users and processes
    • the disk process alone touching sticks
    • a fresh process at Lock in pages the kernel zeroes
    • lockdown and no modules

    One ESP-IDF image in one address space would need a model of its own.

  4. Secure boot. Espressif's advisory AR2026-006 says the P4's ROM ECDSA check may accept invalid signatures, so RSA-3072 secure boot would be used. ESP-IDF is a large body of C that Faraday has not reviewed.

What would decide it

Help is welcome. Before any port, these would be measured on the board:

  • A full frame and a scroll step drawn by faraday-draw
  • Argon2id at 16 MiB
  • A 640 × 480 QR frame read by rqrr
  • A PSBT signed
  • A check, with a scanner, that an erased C6 stays silent

Share a measurementHARDWARE §6.1

Buy me a coffee

Donations to Faraday's development, in bitcoin.

QR code to come
Lightning
QR code to come
Bitcoin