Skip to content

LordOS — a free, fast and secure GNU/Linux distribution based on Debian, with its own desktop environment: display server and Wayland compositor in C, a React UI engine on QuickJS, and private native apps.

Release 0.8.0-beta

Federico Pereiraf4f266db7b1a
diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml
index 6398fc5..75814ee 100644
--- a/.github/ISSUE_TEMPLATE/bug_report.yml
+++ b/.github/ISSUE_TEMPLATE/bug_report.yml
@@ -11,8 +11,8 @@ body:
id: version
attributes:
label: LordOS version
- description: Open the About LordOS app and copy the version (for example "0.7.0 · Beta").
- placeholder: 0.7.0 · Beta
+ description: Open the About LordOS app and copy the version (for example "0.8.0 · Beta").
+ placeholder: 0.8.0 · Beta
validations:
required: true
- type: dropdown
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 8d766f1..35517b8 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -12,7 +12,7 @@ of the matching [GitHub release](https://github.com/lordbasex/LordOS/releases),
Nothing yet.
-## [0.8.0-beta] - TBD
+## [0.8.0-beta] - 2026-10-18
LordOS is a free GNU/Linux distribution based on Debian 13 ("trixie") with its own desktop
environment. Debian provides the kernel, the drivers, Mesa, PipeWire, CUPS, BlueZ and every
@@ -244,6 +244,13 @@ machines, but some parts have not been tested on real hardware yet (see
checks the release signature and SHA-256, installs with apt, sets up the login screen and asks
before switching the display manager; `--uninstall` undoes it
([docs/INSTALL-DEBIAN.md](docs/INSTALL-DEBIAN.md)).
+- **Servers and VPS without a screen:** `curl -fsSL https://lordos.org/install.sh | sh -s -- --remote-desktop`
+ (optionally `--remote-port N`, 1024–65535, default 5673) also turns on the remote desktop, in
+ the same configuration file Settings → Sharing uses, after a confirmation that warns the port
+ accepts logins from the network. Without a display manager the login screen runs headless, so
+ the desktop is reached at `https://<server IP>:5673` from a browser, on amd64 and arm64.
+ `--uninstall` removes the configuration and closes the port
+ ([docs/INSTALL-DEBIAN.md](docs/INSTALL-DEBIAN.md), "Servers and VPS").
- **Boot splash and boot menu:** a LordOS GRUB theme and a Plymouth splash (the crown with a
progress bar) that hands off to the login screen without a black frame or console text.
- **The version and release channel** are built into the system and shown in About and
@@ -267,6 +274,14 @@ machines, but some parts have not been tested on real hardware yet (see
gallery, FAQ, the project paper (with PDFs), the release key and `install.sh`, and complete
legal and trust pages (security policy, code signing, licences, privacy, support lifecycle,
standards and more).
+- **A hero slideshow** of 39 real, checked screenshots inside the laptop on the home page, in
+ story order, with play/pause, previous/next, a counter and captions; it pauses on hover, focus
+ and hidden tabs and respects reduced motion. The spec facts sit in a stats row below it.
+- **Site navigation:** a hamburger menu with a CSS-only drawer on phones (focus trap, Esc), a
+ back-to-top button, a one-slot language dropdown, a dark-mode switch and a centred footer bar;
+ the Debian card covers PCs and servers (amd64 and arm64, with the `--remote-desktop` hint) and
+ the FAQ has an entry on servers and VPS. The site runs under a strict CSP (no inline styles or
+ scripts).
- **Documentation** for every part of the system, indexed in [docs/README.md](docs/README.md),
with the [project paper](docs/PAPER.md) and screenshots from real test runs.
- **Repository policies:** [SECURITY.md](SECURITY.md), [CONTRIBUTING.md](CONTRIBUTING.md),
@@ -295,6 +310,17 @@ machines, but some parts have not been tested on real hardware yet (see
([docs/DESIGN.md](docs/DESIGN.md), before and after screenshots in `docs/polish/`).
- **The boot menu** drops GRUB's countdown bar and uses a tighter selection band.
- **The README** uses the same copy as lordos.org, with measured figures instead of estimates.
+- **Linux apps restricted from the microphone, camera, USB or Bluetooth start in their own view,
+ without the session bus or the user manager** (no notifications or portals for them), so they
+ can't escape their scope. A restriction set while such an app runs applies fully only after the
+ app is restarted; Settings says so ([docs/FIREWALL.md](docs/FIREWALL.md)).
+- **pipewire-pulse doesn't load modules** (`/etc/pipewire/pipewire-pulse.conf.d/lordos-no-modules.conf`):
+ a module loaded by a restricted app would run outside its restrictions. Apps that load PulseAudio
+ modules at run time (`pactl load-module`) get an error.
+- **`kernel.yama.ptrace_scope = 1`** (`/usr/lib/sysctl.d/50-lordos-ptrace.conf`): a process can
+ only trace its own descendants. Debuggers still work on programs they start; attaching to a
+ running process (`gdb -p`, `strace -p`) needs `sudo`.
+- **The copyright holder** is "iPERFEX and the LordOS contributors" (MIT licence unchanged).
### Fixed
@@ -310,6 +336,9 @@ machines, but some parts have not been tested on real hardware yet (see
- The Dock's hit box, audio for newly created users, upgrade-safe helpers, and the login screen now
preselects the last user.
- `lord-server` survives `SIGPIPE` when a client hangs up mid-write.
+- Restarting `lordos.service` left the old login screen running (and, after an upgrade, its old
+ binary); `lord-sessiond` now stops the login screen's processes when it stops and any leftover
+ when it starts ([docs/SESSIONS.md](docs/SESSIONS.md)).
- A crash when a Dock window had no icon.
- The firewall attributed "last matched" to the wrong rule after a save.
- Short connections (such as `curl`) were missing from Monitor → Network; recent destinations are
@@ -352,6 +381,49 @@ described in [SECURITY.md](SECURITY.md).
installer refuses to install when the signature is missing or invalid.
- **Remote desktop** is off by default and only reachable after the owner turns it on.
+Fixed from the security review before this release (high and medium findings; the numbers are
+the review's, in [docs/SECURITY-REVIEW-0.8.0.md](docs/SECURITY-REVIEW-0.8.0.md)):
+
+- **A malicious `.desktop` file could leave the "no access to your files" view** (#1, high): the
+ working directory was entered before the private folders were mounted, so a relative path still
+ reached the real session bus. The directory is now entered inside the view.
+- **An app that couldn't be placed in its own scope still ran, unrestricted** (#2, high), for
+ unusual desktop ids or when lord-sessiond was unreachable. Desktop ids are now limited to safe
+ characters and length, and inside a LordOS session an app that can't be placed never starts.
+- **The microphone guard failed open** (#3, high) when its client or node tables filled up or a
+ permission list was too long. It now disconnects clients it can't follow and destroys streams it
+ can't store.
+- **A restricted app could record the microphone through a PulseAudio module** (#4, high), which
+ ran as the unrestricted pipewire-pulse. Module loading is off (see "Changed").
+- **A restricted Linux app could take over an unrestricted process of the same user with
+ `ptrace`** (#5, high). Only descendants can be traced now (see "Changed").
+- **Restricted Linux apps could escape through the user's own services** (#13, #37, high): two
+ attempts to exempt "the real sound server" under `user@` were forgeable, because the user
+ controls their own systemd manager. Nothing under `user@` is trusted for who it claims to be any
+ more; apps restricted from the microphone, camera, USB or Bluetooth start in their own view
+ instead (see "Changed"), and the desktop keeps its microphone.
+- **"Open with" could hand an app protected folders** (#6, medium) such as `~/.config/autostart`,
+ `firewall.json` or `~/.ssh` when a parent folder was opened, and **a symlink swapped in between
+ the check and the grant** could redirect it (#10, medium). Writable grants never cover those
+ folders, hard-linked files are read-only, and the grant is reopened without following symlinks
+ and must still be the checked file.
+- **Shared memory, terminals and caches of the session were reachable** from the files view (#7,
+ #8, medium): it now has its own `/dev/shm`, its own pseudo-terminals and IPC namespace, and the
+ font, shader and GStreamer caches are read-only. More folders that other programs run code from
+ are protected (#9), and a missing `XDG_RUNTIME_DIR` no longer leaves the bus reachable (#11).
+- **A USB microphone plugged in while a no-mic app ran** was open to it for a few seconds (#12,
+ medium): every sound device not known to be playback-only is now denied in its scope.
+- **A user process could pose as the sound server** to the microphone guard (#14, #15, #16,
+ medium) with a nested cgroup or another PID namespace. Matching is now exact (cgroup path, sole
+ process, root-owned binary, our PID namespace).
+- **The last frame of another user's desktop could be read after a user switch** (#17, medium):
+ lord-sessiond now removes the leaving session's framebuffers before handing the screen over.
+- **Landlock's socket scoping failed open on older kernels** (#38, medium): the files view and the
+ device view now require Landlock ABI 6 and refuse to start the app otherwise, with a notification.
+- **Installer and release tools** (low): the verified package is reinstalled from a root-owned
+ copy, a missing release key is an error, a validly signed older release can't downgrade an
+ install, and the signing script refuses unexpected file names.
+
### Known issues and limitations
- **Xwayland is not supported:** apps that only speak X11 don't start (planned before 1.0).
diff --git a/package-lock.json b/package-lock.json
index b5e8a93..4bc3cd3 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -1,12 +1,12 @@
{
"name": "lordos",
- "version": "0.7.0",
+ "version": "0.8.0",
"lockfileVersion": 3,
"requires": true,
"packages": {
"": {
"name": "lordos",
- "version": "0.7.0",
+ "version": "0.8.0",
"dependencies": {
"react": "19.3.1",
"react-reconciler": "0.34.0"
diff --git a/package.json b/package.json
index 7914660..2b500f5 100644
--- a/package.json
+++ b/package.json
@@ -1,7 +1,7 @@
{
"name": "lordos",
"private": true,
- "version": "0.7.0",
+ "version": "0.8.0",
"description": "LordOS — React themes and apps for lord-server",
"lordos": {
"channel": "beta"
diff --git a/runtime/index.js b/runtime/index.js
index a13a5dc..9a665a6 100644
--- a/runtime/index.js
+++ b/runtime/index.js
@@ -89,7 +89,7 @@ let updatePriority = NoEventPriority;
// react-reconciler 0.34 host interface (React 19), mutation mode like React Native.
const host = {
rendererPackageName: '@lordos/runtime',
- rendererVersion: '0.7.0',
+ rendererVersion: '0.8.0',
supportsMutation: true,
supportsPersistence: false,
supportsHydration: false,
diff --git a/sdk/system.js b/sdk/system.js
index 008540f..729d5d4 100644
--- a/sdk/system.js
+++ b/sdk/system.js
@@ -5,7 +5,7 @@ import { formatNumber, t } from './i18n.js';
export const systemInfo = () => lord.system.info();
// LordOS's own version, from the build (package.json "version" and "lordos": {"channel"}, see
-// server/Makefile): { version: '0.7.0', channel: 'Beta' (empty for a stable release), build }.
+// server/Makefile): { version: '0.8.0', channel: 'Beta' (empty for a stable release), build }.
export function lordosVersion(info) {
const i = info || systemInfo();
const id = String(i.channel || '');
diff --git a/server/Makefile b/server/Makefile
index eb2a214..a2dd3ae 100644
--- a/server/Makefile
+++ b/server/Makefile
@@ -414,7 +414,7 @@ build/gen/lord_version.h: FORCE
@printf '#define LORD_VERSION "%s"\n#define LORD_CHANNEL "%s"\n#define LORD_BUILD "%s"\n' \
'$(or $(LORD_VERSION),0.0.0)' '$(LORD_CHANNEL)' '$(shell printf %s '$(LORD_BUILD)' | tr -cd 'A-Za-z0-9.+~-')' > [email protected]
@if cmp -s [email protected] $@; then rm -f [email protected]; else mv [email protected] $@; fi
-build/obj/ui/js.o build/obj/ui/js_sys.o: build/gen/lord_version.h
+build/obj/ui/js.o build/obj/ui/js_sys.o build/obj/term/pty.o: build/gen/lord_version.h
.PHONY: FORCE
FORCE:
diff --git a/server/src/term/pty.c b/server/src/term/pty.c
index b1c0e8d..e0c9a83 100644
--- a/server/src/term/pty.c
+++ b/server/src/term/pty.c
@@ -4,6 +4,7 @@
* login shell (the one in /etc/passwd), just like any terminal emulator.
* The child inherits no capabilities, blocked signals or descriptors from the server. */
#include "term.h"
+#include "lord_version.h" /* build/gen: LordOS version (Makefile, from package.json) */
#include <errno.h>
#include <fcntl.h>
@@ -67,7 +68,7 @@ static void child(int fd, const char *cwd, int id) {
setenv("TERM", "xterm-256color", 1);
setenv("COLORTERM", "truecolor", 1);
setenv("TERM_PROGRAM", "LordTerminal", 1);
- setenv("TERM_PROGRAM_VERSION", "0.7.0", 1);
+ setenv("TERM_PROGRAM_VERSION", LORD_VERSION, 1);
setenv("LORD_TERMINAL_SESSION", idbuf, 1);
setenv("SHELL", shell, 1);
if (pw) { setenv("USER", pw->pw_name, 1); setenv("LOGNAME", pw->pw_name, 1); }
diff --git a/web/content/legal/issues.en.md b/web/content/legal/issues.en.md
index 90b1c23..cb6cfd9 100644
--- a/web/content/legal/issues.en.md
+++ b/web/content/legal/issues.en.md
@@ -13,7 +13,7 @@ Before you write, check the [FAQ](/faq/) and, once they are public, the existing
## What to include in a bug report
-- **The LordOS version**, as shown in the About LordOS app (for example "0.7.0 · Beta").
+- **The LordOS version**, as shown in the About LordOS app (for example "0.8.0 · Beta").
- **How you installed it:** the ISO (live or installed), the Raspberry Pi 5 image, or the `.deb` on Debian 13.
- **Your hardware:** the computer or board model, the graphics card, the amount of memory, and any device involved (printer, touchpad, Wi-Fi adapter, monitor).
- **Steps to reproduce:** what you did, one step per line, starting from a fresh start if you can.
diff --git a/web/content/legal/issues.es.md b/web/content/legal/issues.es.md
index baa92aa..05bc67a 100644
--- a/web/content/legal/issues.es.md
+++ b/web/content/legal/issues.es.md
@@ -13,7 +13,7 @@ Antes de escribir, revisá las [preguntas frecuentes](/faq/) y, cuando sean púb
## Qué incluir en un reporte de error
-- **La versión de LordOS**, como aparece en la app Acerca de LordOS (por ejemplo "0.7.0 · Beta").
+- **La versión de LordOS**, como aparece en la app Acerca de LordOS (por ejemplo "0.8.0 · Beta").
- **Cómo la instalaste:** la ISO (live o instalada), la imagen para Raspberry Pi 5 o el `.deb` en Debian 13.
- **Tu hardware:** el modelo de la computadora o de la placa, la placa de video, la memoria y cualquier dispositivo que tenga que ver (impresora, touchpad, adaptador Wi-Fi, monitor).
- **Pasos para reproducirlo:** qué hiciste, un paso por línea, desde un arranque limpio si podés.
diff --git a/web/content/legal/issues.pt.md b/web/content/legal/issues.pt.md
index 0cbd4e6..4a860a7 100644
--- a/web/content/legal/issues.pt.md
+++ b/web/content/legal/issues.pt.md
@@ -13,7 +13,7 @@ Antes de escrever, veja as [perguntas frequentes](/faq/) e, quando forem públic
## O que incluir num relato de bug
-- **A versão do LordOS**, como aparece no app Sobre o LordOS (por exemplo "0.7.0 · Beta").
+- **A versão do LordOS**, como aparece no app Sobre o LordOS (por exemplo "0.8.0 · Beta").
- **Como você instalou:** a ISO (live ou instalada), a imagem para Raspberry Pi 5 ou o `.deb` no Debian 13.
- **O seu hardware:** o modelo do computador ou da placa, a placa de vídeo, a quantidade de memória e qualquer dispositivo envolvido (impressora, touchpad, adaptador Wi-Fi, monitor).
- **Passos para reproduzir:** o que você fez, um passo por linha, a partir de uma inicialização limpa se possível.
diff --git a/web/content/legal/security.en.md b/web/content/legal/security.en.md
index ecd843b..cb8e7e6 100644
--- a/web/content/legal/security.en.md
+++ b/web/content/legal/security.en.md
@@ -6,7 +6,7 @@ Write to us through **[our contact form](https://www.iperfex.com/contacto/?lang=
Include, as far as you can:
-- the LordOS version (shown in the About LordOS app, for example "0.7.0 · Beta") and whether it is the ISO, the Raspberry Pi image or the Debian package;
+- the LordOS version (shown in the About LordOS app, for example "0.8.0 · Beta") and whether it is the ISO, the Raspberry Pi image or the Debian package;
- the component affected (for example the compositor, the app sandbox, the per-app firewall, remote desktop, the password vault, the Store, the Debian installer script or the website);
- the steps to reproduce it, a proof of concept if you have one, and the impact you see;
- how you'd like to be credited, if at all.
diff --git a/web/content/legal/security.es.md b/web/content/legal/security.es.md
index 305a852..6465a9f 100644
--- a/web/content/legal/security.es.md
+++ b/web/content/legal/security.es.md
@@ -6,7 +6,7 @@ Escribinos por **[nuestro formulario de contacto](https://www.iperfex.com/contac
Incluí, en la medida de lo posible:
-- la versión de LordOS (la ves en la app Acerca de LordOS, por ejemplo "0.7.0 · Beta") y si es la ISO, la imagen para Raspberry Pi o el paquete para Debian;
+- la versión de LordOS (la ves en la app Acerca de LordOS, por ejemplo "0.8.0 · Beta") y si es la ISO, la imagen para Raspberry Pi o el paquete para Debian;
- el componente afectado (por ejemplo el compositor, el aislamiento de apps, el firewall por app, el escritorio remoto, la bóveda de contraseñas, la Tienda, el script de instalación para Debian o el sitio);
- los pasos para reproducirlo, una prueba de concepto si la tenés, y el impacto que ves;
- cómo te gustaría que te mencionemos, si querés que lo hagamos.
diff --git a/web/content/legal/security.pt.md b/web/content/legal/security.pt.md
index 71de599..fbcfaae 100644
--- a/web/content/legal/security.pt.md
+++ b/web/content/legal/security.pt.md
@@ -6,7 +6,7 @@ Escreva pelo **[nosso formulário de contato](https://www.iperfex.com/contacto/?
Inclua, na medida do possível:
-- a versão do LordOS (no app Sobre o LordOS, por exemplo "0.7.0 · Beta") e se é a ISO, a imagem para Raspberry Pi ou o pacote do Debian;
+- a versão do LordOS (no app Sobre o LordOS, por exemplo "0.8.0 · Beta") e se é a ISO, a imagem para Raspberry Pi ou o pacote do Debian;
- o componente afetado (por exemplo o compositor, o sandbox de apps, o firewall por app, a área de trabalho remota, o cofre de senhas, a Loja, o script de instalação para Debian ou o site);
- os passos para reproduzir, uma prova de conceito se você tiver, e o impacto que você vê;
- como você gostaria de ser creditado, se quiser.