Repository navigation
LordOS 0.8.4-beta
Pre-release
Pre-release
Added
- Settings → Appearance → «Browsers: tabs in the title bar». One switch for both preinstalled browsers: on (the default), Chromium and Firefox draw a single bar with their tabs and LordOS's window buttons; off, they use the LordOS frame. It changes the setting in your own browser profiles and applies the next time each browser opens; if Chromium is open, it waits until you quit it. Chromium profiles from before this version that still use the LordOS frame are shown on the page, with a button to change them too. A choice you made yourself in a Firefox
user.jsfile is left alone, and choices you make later in the browsers' own settings stick. - Remote desktop as video. The remote desktop now arrives as real video (H.264, or VP8 when the browser has no H.264) with the session's sound (Opus), instead of images. Still areas are then made pixel-perfect with lossless tiles, so text stays sharp. Dragging a window went from about 23 frames per second and 12.5 Mbit/s to about 29 frames per second and under 1 Mbit/s, and the connection's own process from 57 % of a core to 2 %. The session encodes once (on the graphics card with VA-API when it can, else in software) for every viewer of that session; the screen keeps being composed on the graphics card while someone watches. Keyboard, mouse and clipboard go over a WebRTC data channel. Video is the only way the remote desktop works (see Removed).
- The remote desktop works where UDP is blocked. Besides UDP, the video also connects over TCP on the remote desktop's own port (5673), so a firewall or VPN that only lets that port through is enough; on the local network nothing else is needed. With UDP blocked, video plays about 2 s after the page loads.
- The remote desktop reconnects by itself. When the network drops or changes, the page keeps the last frame with a "Reconnecting…" note and recovers on its own, without signing in again: first on the same encrypted connection (back within a fraction of a second once the network returns, after a 20-second outage), then with a new one, then with a new connection to the computer after longer outages (75 seconds were tested).
- Clear messages when it can't connect. If there is really no way through, the page says why (nothing gets through over UDP or TCP, the encrypted channel couldn't be set up, the connection was lost, the browser can't play the video…) and what to do, with a Try again button. A browser without WebRTC, or without H.264 and VP8, gets a page that lists what it needs.
- Settings → Sharing → Connection: add public STUN servers and a TURN relay for connecting across networks, reached over UDP, TCP or TLS (port 443 works). Over TLS the relay's certificate is checked against the system's certificate authorities and its name, or against a fingerprint you paste for a relay with its own certificate. A built-in STUN server covers the local network, and nothing reaches outside servers unless you add them. The relay's password stays on the computer, readable only by the system, and is never sent to the browser.
- LordOS Imager. Write LordOS to an SD card or a USB stick and have the Raspberry Pi 5 start ready to use: choose the device (Raspberry Pi 5, or a PC from a USB stick), the system image (the latest signed release, downloaded once and resumed if interrupted, or a file of your own with a clear warning) and the drive (only SD cards and USB drives; internal disks and the disk the computer runs from are never shown), then customise the first boot: computer name, language, time zone, keyboard, your account (only a hash of the password goes on the card), Wi-Fi (only the derived key), SSH with keys or a password, LordOS remote desktop (local network only), Bluetooth, Lord Default or Classic in light or dark with your accent, and cooling (case with a fan, active cooler, passive case or nothing, with a matching profile and an optional mild overclock with a fan). Lumo gives a tip at every step and celebrates at the end. Every official image is checked against the LordOS release signature before anything is erased, and every card is read back and compared after writing; cancelling clears the card. In English, Spanish and Portuguese, with keyboard navigation. See docs/IMAGER.md.
- The LordOS Imager for other computers: the same app for the three common desktop platforms (Tauri, about 6 MB), sharing the interface with the one in LordOS, attached to this release as
lordos_imager_0.8.4_universal.dmg(both processor families, signed and notarized, so it opens without warnings),lordos_imager_0.8.4_amd64.deb(needs udisks2 and a polkit agent) andlordos_imager_0.8.4_x64_setup.exe(not code-signed yet, see Known issues), all listed in the signedSHA256SUMS. - First-run file on the Raspberry Pi (
lordos-firstrun.txton the boot partition): read once on the first boot bylordos-firstrun, strictly validated (nothing is applied if any part is wrong), then overwritten and deleted. See docs/RASPBERRY.md, "First boot".
Security
- The imager's privileged part is four closed actions: downloads run
curlas the user against two fixed URL shapes; writing accepts only a whole removable disk whose size, model and serial are re-checked right before it is opened exclusively, decompresses withxzrunning as the user, and never writes an official image whose signature or hash doesn't match. Over 2 TiB is refused. - Saved Wi-Fi networks may hold a derived WPA2 key (
psk=) instead of the password.
Changed
- Browsers with a single top bar. Chromium and Firefox now draw their own bar, with the tabs in the title bar and the window buttons inside it, instead of the LordOS frame on top. In Chromium the buttons are LordOS's traffic lights (from LordOS's GTK theme, sized like LordOS's own frame); Firefox keeps its own button style. Both put them where the LordOS theme does: on the left in Lord Default, on the right in Classic, and follow a theme or light/dark change live. Going back to the LordOS frame is one switch in each browser («Use system title bar and borders» in Chromium, «Title Bar» in Firefox), and it now applies right away, without reopening the window. Systems upgraded from 0.8.3 get the new defaults for Firefox, and for new Chromium profiles; an existing Chromium profile keeps its frame until its user switches (or uses the new switch in Settings).
Removed
- The remote desktop's image mode. The screen no longer travels as PNG/JPEG images over the connection to the browser, not even as a fallback: it is WebRTC video, which reconnects on its own and explains any failure instead. The «images only» switch in Settings → Sharing is gone, and
lord-sessiondnow always needs libsrtp2 and usrsctp (thelordospackage depends onlibsrtp2-1andlibusrsctp2). While the video plays the CPU use is the same as before (the image path was already idle then); what's gone is the image work before the video starts and on networks where the video couldn't connect.
Fixed
- Raspberry Pi 5 on an HDMI monitor: "LordOS could not show its desktop" on the first boot. The login screen gave up when the display driver (vc4) wasn't there yet as LordOS started, and the board stayed on the text console. LordOS now loads the driver itself and waits up to 30 s for it, and the session waits up to 30 s more for a display device before falling back.
- Two title bars in Chromium. With «Use system title bar and borders» off, Chromium drew its own bar and LordOS still put its frame on top: the compositor now honors the frame an app asks for (xdg-decoration and the GTK 3 decoration protocol), also when it changes while the window is open; the window keeps its place, size, maximized state, focus and Dock entry.
- Linux app windows disappeared after switching between Lord Default and Classic (they stayed open but invisible): they now come back in the new theme, maximized ones still maximized.
- The window menu of apps that draw their own bar. A right click on a GTK app's own title bar now opens the theme's window menu (Minimize, Zoom, Close; in Classic also Restore, Snap layouts and the snap halves).
- Raspberry Pi 5: blocking an app now closes its open connections (a known issue in 0.8.3), as on a PC, instead of leaving them stalled until the app's own timeout. The LordOS Pi kernel is rebuilt as
6.18.57-lordos.3-rpi-2712(6.18.57-3+lordos): the same Raspberry Pi source and options as before (Landlock, the BPF LSM, BTF, Yama) plus sock_diag socket destroy (CONFIG_INET_DIAG_DESTROY,CONFIG_INET_UDP_DIAG), solord-netpermcloses TCP and QUIC connections a new rule denies within a fraction of a second. Each kernel revision now installs as its own package next to the previous one, so the previous kernel stays bootable as a fallback (one line inconfig.txt, see docs/RASPBERRY.md). The image build andverify-boardcheck the kernel has it. On a Pi 5: TCP downloads and an idle session end 0.04–0.37 s after the rule changes, an HTTP/3 (QUIC) download 0.08 s. build-kernel.shcross-compiles the Pi kernel on an x86-64 Debian 13 (the arm64 Debian packages, no arm64 build dependencies needed).
Known issues and limitations
- The remote desktop needs a browser with WebRTC and H.264 or VP8 video. Current desktop and mobile browsers have both; a browser without them gets a page that lists what it needs, since the image mode is gone (see Removed).
- The Raspberry Pi 5 image is the 0.8.4.1 one (
lordos-0.8.4.1-rpi5-arm64.img.xz, added on 25 October 2026 after it was booted on a board with an HDMI monitor; the same file as in v0.8.4.1-beta, listed in this release's re-signedSHA256SUMS). It is here so LordOS Imager 0.8.4, which doesn't recognise four-number releases, offers it too (it shows it as LordOS 0.8.4). The Imager downloads were rebuilt the same day with that fix (same names, new hashes inSHA256SUMS); download them again to see newer releases by their own number. - Raspberry Pi 5 boards updated from the Store or
aptkeep their kernel. The LordOS Pi kernel is not in the APT repository yet (docs/UPDATES.md, "The Raspberry Pi kernel"), so the-3kernel, which closes the connections of a blocked app, comes with the next Pi image. On a board with the-2kernel the firewall still drops a blocked connection's packets, but the app only sees it end at its own timeout, as in 0.8.3. - The LordOS Imager: the desktop downloads were tested writing to disk images, not yet to real SD cards or USB sticks; the first-run file was applied to the 0.8.4 Pi image in a test (every setting checked), not yet booted on a board. The installer for the third platform is not code-signed yet, so the system warns before running it the first time; its SHA-256 is in the signed
SHA256SUMS. Images up to 0.8.3 ignore the first-run file and start in setup mode. - Existing Chromium profiles keep the LordOS frame until you switch them (Settings → Appearance lists them, with a button); new profiles and Firefox get the single bar.
- Monitor → Network's second generation, listed for 0.8.4 in the roadmap, is not in this release.
- The other known issues of 0.8.3 still apply.
Upgrading
- From 0.8.3, 0.8.2 or 0.8.1: Store → Updates shows "LordOS 0.8.4 is available" with these notes; Update installs it (with its two new libraries,
libsrtp2-1andlibusrsctp2), and a restart finishes it.sudo apt update && sudo apt upgradedoes the same (apt-get upgradekeepslordosback because of the new dependencies;apt upgradeorapt-get install lordosinstalls it). The update runs migration 005 once (the preinstalled browsers' default bar; from older versions the earlier migrations run first);ls /var/lib/lordos/migrationslists the ones applied. Your settings are kept. - Browsers after the update: Firefox draws its single bar the next time it opens (unless you chose «Title Bar» yourself); new Chromium profiles do too. To get it in an existing Chromium profile, or to go back to the LordOS frame for both, use Settings → Appearance → «Browsers: tabs in the title bar».
- Remote desktop after the update: it is WebRTC video only. The «images only» switch is gone from Settings → Sharing; nothing else changes in its settings (port, addresses, the lockout). Where only the remote desktop's port is open, the video now connects over TCP on that port.
- Raspberry Pi 5:
lordosupdates from the Store oraptlike on a PC. The-3kernel comes with the next Pi image (see Known issues); on an updated boarduname -rstill shows6.18.57-lordos-rpi-2712. Building and installing it by hand next to the old one is described indocs/RASPBERRY.md, "Switching kernels on a board". - From 0.8.0 (once): run
curl -fsSL https://lordos.org/install.sh | sh(a system installed from the 0.8.0 ISO has nocurl: runsudo apt update && sudo apt install -y curlfirst). It upgrades in place to 0.8.4, runs migrations 001 to 005 and adds the LordOS repository; from then on new versions come through Store → Updates.
Downloads
| File | What it is |
|---|---|
lordos-live-0.8.4-amd64.iso |
Live and installable image for 64-bit PCs (UEFI and BIOS). Write it to a USB stick as is; Secure Boot off. |
lordos_0.8.4_amd64.deb |
The LordOS package for an existing Debian 13 on a PC (installed by install.sh, or with apt install ./…). |
lordos_0.8.4_arm64.deb |
The same package for Debian 13 on arm64. |
lordos_imager_0.8.4_universal.dmg |
LordOS Imager for Mac (both processor families, signed and notarized): writes LordOS to an SD card or a USB stick and prepares the Raspberry Pi 5's first boot. |
lordos_imager_0.8.4_x64_setup.exe |
LordOS Imager for Windows (64-bit installer; not code-signed yet, so the system asks before running it). |
lordos_imager_0.8.4_amd64.deb |
LordOS Imager for Linux (Debian 13 and similar, amd64; needs udisks2). |
install.sh |
The one-line installer for Debian 13: curl -fsSL https://lordos.org/install.sh | sh. It checks the signature before installing. |
SHA256SUMS |
The SHA-256 of every file in this release. |
SHA256SUMS.sig |
The Ed25519 signature of SHA256SUMS with the LordOS release key (base64). |
lordos_0.8.4_<arch>.spdx.json |
Software bill of materials (SPDX 2.3) for each package: what it bundles and the Debian packages it depends on. |
Verifying the downloads
The LordOS release public key is lordos-release.pub.pem (in the repository, or at https://lordos.org/lordos-release.pub.pem). Its fingerprint, the SHA-256 of the DER public key, is:
c7155b8e6bbbb180f907381994d06af76d333016cd6f3facf67cadd053ea108e
With OpenSSL 3, in the folder with the downloads:
openssl pkey -pubin -in lordos-release.pub.pem -outform DER | sha256sum # must match the fingerprint
base64 -d SHA256SUMS.sig > SHA256SUMS.sig.bin
openssl pkeyutl -verify -pubin -inkey lordos-release.pub.pem -rawin -in SHA256SUMS -sigfile SHA256SUMS.sig.bin
sha256sum -c --ignore-missing SHA256SUMS"Signature Verified Successfully" and "OK" for each downloaded file mean the files are the ones we published. Details: docs/SIGNING.md.
Links
- Website: lordos.org
- The project paper: lordos.org/paper
- Documentation: docs/README.md
- Security policy and reporting a vulnerability: lordos.org/legal/security
- Full changelog: CHANGELOG.md