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.
C cdebiandesktop-environmentebpffirewalllandlocklinuxlinux-distributionopen-sourceprivacyquickjsraspberry-pi-5reactsecuritywaylandwayland-compositor
Integration 0.8.2: one CHANGELOG section, VM-SETUP steps renumbered, migration 003 in UPDATES.md
Federico Pereirad5a33a4ee0f4
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 8014405..a24e5a3 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -8,10 +8,33 @@ suffix (`-beta`) and are published on GitHub as pre-releases. Each section belowof the matching [GitHub release](https://github.com/lordbasex/LordOS/releases), generated by`tools/release/release-notes.sh` (see [docs/RELEASING.md](docs/RELEASING.md)).+## [Unreleased]+## [0.8.2] - Unreleased### Added+- **New wallpapers.** Eleven original LordOS wallpapers in three categories: **Signature** (Crystal+ Crown, Eternal Dawn, Royal Flow, Royal Waves, Violet Horizon), **Lumo** (Celestial, Aurora) and+ **Cosmos** (Event Horizon, Infinite Galaxy, Solar Odyssey, Stellar Voyage), created by iPERFEX+ with an AI image generator. Settings → Wallpaper now lists every wallpaper grouped by category,+ with the previous four gradients as "Gradients". They are installed once in+ `/usr/share/backgrounds/lordos/` as high-quality JPEG (about 4 MB in total) with small thumbnails+ for the pickers, and a higher-resolution version added later is used automatically on the+ screens that need it.+- **Suggested for your computer.** Store → Discover now starts with packages for the hardware+ LordOS finds in the computer, each with the reason it appears ("We detected a printer from HP+ connected by USB"): the guest tools of a VMware or QEMU virtual machine, the proprietary graphics+ driver for an NVIDIA card (labeled as not free software, never preselected, with what changes:+ DKMS, Secure Boot key enrollment, older cards, and that the free nouveau driver stays the+ default), vendor drivers for USB printers and scanners, driverless USB printing (`ipp-usb`),+ the Raspberry Pi 5's board tools, and the firmware package a Wi-Fi, Bluetooth, network or+ graphics device asked for and didn't find. One click shows the usual plan and installs through+ the package engine; "Don't suggest again" hides a card for good. When something new is+ suggested, the Store's Discover item shows a count and one notification says so. For a+ VirtualBox virtual machine the card explains that its guest utilities aren't part of Debian 13.+ Detection only reads the kernel's hardware files; nothing is sent anywhere. The rules are data+ (`assets/store/suggestions.json`); see [docs/PACKAGES.md](docs/PACKAGES.md).- **Monitor → Disks: each disk's temperature and health.** The Disks tab now shows every physicaldisk's live temperature, read from the kernel without root: NVMe and M.2 drives through the nvmedriver's own sensor (also on a Raspberry Pi 5 with an M.2 HAT), SATA disks through the `drivetemp`@@ -49,47 +72,28 @@ of the matching [GitHub release](https://github.com/lordbasex/LordOS/releases),action `video-optimize` (fixed text, no user text). Firefox ESR only loads signed extensions, sofor now it gets AV1 turned off through a default preference (it then uses VP9); the extensionfor Firefox waits for signing.-### Security--- **LordOS checks its own code before running it.** Every bundle LordOS runs as its own code — the- themes with the shell and every native app, the login screen, the app host of isolated apps and- the system apps that run as their own process — is listed with its SHA-256 in- `/usr/lib/lordos/code-manifest.json`, signed with the LordOS release key (Ed25519).- lord-server verifies the signature with the public key compiled in, and the hash of each bundle- as it loads it, from the same read (no window to swap the file). A bundle that doesn't match is- not run: the desktop falls back to another theme and shows "This LordOS component was modified and- was not loaded"; with nothing left to load (or at the login screen) a built-in recovery screen- explains it and how to repair it, never a blank screen. It protects against changes by non-root- processes and offline modification; root can still replace lord-server itself, which phase 3- (fs-verity, A/B images) will cover. Cost on a session start: about 7 ms on a Raspberry Pi 5,- 18–34 ms on a 1.8 GHz Xeon VM- ([docs/SIGNING.md](docs/SIGNING.md#verified-system-code-082)).-- **System apps can't be removed.** Store → Installed shows "System app — part of LordOS" instead- of Remove for the apps that come with LordOS, and the `lordos` package is marked `Protected` so the- Store's package engine refuses to remove it.--### Added-+- **Allow or block each destination inside Monitor's app rows.** Open an app in Monitor → Network+ and every name it reached (or address, when the system resolver gave no name) has its own+ allow/block switch, showing what the app's rules decide for it right now and why ("By the rule+ \*.example.com", "Follows this app's default", "Blocked by this app's restrictions"). A click+ writes, flips or removes the rule for exactly that name, the same rule Settings → Privacy →+ Network rules by app shows, and `lord-netperm` applies it at once. Long lists show eight and+ "N more…"; rows keep their place while the list is open+ ([docs/MONITOR.md](docs/MONITOR.md#per-destination-switches-082)).+- **Traffic history.** The Network tab's chart now zooms out from the live minute to 1 hour,+ 24 hours, 7 days and 30 days, steps back and forward one window at a time and has **Now**; with+ an app selected its own chart follows the same window, and the summary lists the apps that moved+ the most in it. Your session records bytes received and sent per minute (7 days) and per hour+ (30 days), for the computer and for each of your apps, in a small file in your home folder+ (`~/.local/state/lordos/net-history.bin`): never an address, a name or a country. Settings →+ Privacy → Monitor has **Keep a traffic history** (on) and **Clear History**+ ([docs/MONITOR.md](docs/MONITOR.md#traffic-history-082)).- About LordOS shows a "System app" badge and the state of the system code: "Verified", or"Development build" for an unsigned development tree.- `lord-server --check-code [<folder>]` checks a whole installed tree against the signed manifest(troubleshooting, and the `.deb` build).- SHA-256 uses the CPU's SHA-256 instructions on the Raspberry Pi 5 (5× faster there), and theportable code is about twice as fast.--### Changed--- Releases: `tools/release/sign-code.sh` signs the system-code manifest on the maintainer's machine- before the build; `make -C server RELEASE=1` builds a lord-server that only runs signed code, and- `tools/iso/mkdeb.sh` refuses to package bundles that don't match- ([docs/RELEASING.md](docs/RELEASING.md)).--## [Unreleased]--## [0.8.2] - Unreleased--### Added-- **Design study: an immutable LordOS with A/B system images** ([docs/IMMUTABLE.md](docs/IMMUTABLE.md)).It compares dm-verity system partitions, fs-verity, composefs, OSTree, A/B root partitions andbtrfs snapshots against Debian 13, the Store, the Raspberry Pi 5 and LordOS's threat model, and@@ -102,14 +106,6 @@ of the matching [GitHub release](https://github.com/lordbasex/LordOS/releases),update into the other slot, and a scripted demonstration in which a deliberately broken versionfails three times and the machine returns to the previous version on its own. Its payload is aminimal Debian 13, not the LordOS desktop yet; the rest of the plan moves to later versions.-- **New wallpapers.** Eleven original LordOS wallpapers in three categories: **Signature** (Crystal- Crown, Eternal Dawn, Royal Flow, Royal Waves, Violet Horizon), **Lumo** (Celestial, Aurora) and- **Cosmos** (Event Horizon, Infinite Galaxy, Solar Odyssey, Stellar Voyage), created by iPERFEX- with an AI image generator. Settings → Wallpaper now lists every wallpaper grouped by category,- with the previous four gradients as "Gradients". They are installed once in- `/usr/share/backgrounds/lordos/` as high-quality JPEG (about 4 MB in total) with small thumbnails- for the pickers, and a higher-resolution version added later is used automatically on the- screens that need it.### Changed@@ -117,45 +113,6 @@ of the matching [GitHub release](https://github.com/lordbasex/LordOS/releases),keeps it. The login screen (and the remote login page) now shows **Crystal Crown**.- The Control Center shows the current wallpaper and three from the collection; the rest are inSettings → Wallpaper (**Change Wallpaper…**).-- **Suggested for your computer.** Store → Discover now starts with packages for the hardware- LordOS finds in the computer, each with the reason it appears ("We detected a printer from HP- connected by USB"): the guest tools of a VMware or QEMU virtual machine, the proprietary graphics- driver for an NVIDIA card (labeled as not free software, never preselected, with what changes:- DKMS, Secure Boot key enrollment, older cards, and that the free nouveau driver stays the- default), vendor drivers for USB printers and scanners, driverless USB printing (`ipp-usb`),- the Raspberry Pi 5's board tools, and the firmware package a Wi-Fi, Bluetooth, network or- graphics device asked for and didn't find. One click shows the usual plan and installs through- the package engine; "Don't suggest again" hides a card for good. When something new is- suggested, the Store's Discover item shows a count and one notification says so. For a- VirtualBox virtual machine the card explains that its guest utilities aren't part of Debian 13.- Detection only reads the kernel's hardware files; nothing is sent anywhere. The rules are data- (`assets/store/suggestions.json`); see [docs/PACKAGES.md](docs/PACKAGES.md).--### Fixed--- **Package lists after enabling a component.** Adding a component (such as `non-free-firmware`)- or a source whose signed release file hadn't changed upstream left the package list as it was- ("already up to date"); the index is now rebuilt whenever the set of lists it is built from- changes.-- **Allow or block each destination inside Monitor's app rows.** Open an app in Monitor → Network- and every name it reached (or address, when the system resolver gave no name) has its own- allow/block switch, showing what the app's rules decide for it right now and why ("By the rule- \*.example.com", "Follows this app's default", "Blocked by this app's restrictions"). A click- writes, flips or removes the rule for exactly that name, the same rule Settings → Privacy →- Network rules by app shows, and `lord-netperm` applies it at once. Long lists show eight and- "N more…"; rows keep their place while the list is open- ([docs/MONITOR.md](docs/MONITOR.md#per-destination-switches-082)).-- **Traffic history.** The Network tab's chart now zooms out from the live minute to 1 hour,- 24 hours, 7 days and 30 days, steps back and forward one window at a time and has **Now**; with- an app selected its own chart follows the same window, and the summary lists the apps that moved- the most in it. Your session records bytes received and sent per minute (7 days) and per hour- (30 days), for the computer and for each of your apps, in a small file in your home folder- (`~/.local/state/lordos/net-history.bin`): never an address, a name or a country. Settings →- Privacy → Monitor has **Keep a traffic history** (on) and **Clear History**- ([docs/MONITOR.md](docs/MONITOR.md#traffic-history-082)).--### Changed-- **The map's moving dots cost about half as much.** lord-server now repaints several smallrectangles per frame instead of the one box around every change, skips clipped parts of theinterface outside them, and copies only those rectangles to the screen; the dots are small@@ -163,11 +120,27 @@ of the matching [GitHub release](https://github.com/lordbasex/LordOS/releases),from 2.9 to 1.6 points of one core (VM 119, CPU compositing), and every partial repaint of thedesktop gets cheaper the same way. Blurred surfaces (the menu bar, the Dock) are still repaintedwhole when anything touches them, as in 0.8.1 ([docs/MONITOR.md](docs/MONITOR.md#082-several-damaged-rectangles-vm-119)).+- Isolated apps start faster: the app host is compiled to bytecode once per session, so an app's+ JavaScript loads in ~23 ms instead of ~110 ms (Mail's window: ~145 ms from the click to its first+ frame on a 1.8 GHz test machine).+- The Dock's quick actions and **New window** now work for the apps that run in their own process;+ Passwords stays a single window.+- An isolated app's process is named after the app (`mail`), not `exe`, in `ps` and Monitor.+- Releases: `tools/release/sign-code.sh` signs the system-code manifest on the maintainer's machine+ before the build; `make -C server RELEASE=1` builds a lord-server that only runs signed code, and+ `tools/iso/mkdeb.sh` refuses to package bundles that don't match+ ([docs/RELEASING.md](docs/RELEASING.md)).-### Not included+### Fixed++- **Package lists after enabling a component.** Adding a component (such as `non-free-firmware`)+ or a source whose signed release file hadn't changed upstream left the package list as it was+ ("already up to date"); the index is now rebuilt whenever the set of lists it is built from+ changes.+- Isolated apps showed times in UTC instead of the local time zone.+- Trusting a self-signed certificate for an SMTP server on port 465 pinned it as the IMAP server's,+ so sending kept failing.-- **City names on the map.** Debian 13 only ships country-level IP databases (`geoip-database`) and- LordOS's own is country-level too, so labels stay countries; no large download was added.### Security- **Mail, Calendar, Contacts and Reminders run in their own sandboxed process.** Like Passwords@@ -180,21 +153,27 @@ of the matching [GitHub release](https://github.com/lordbasex/LordOS/releases),Notifications, alarms, Dock quick actions, several windows and opening attachments keep working.Monitor shows each app as its own process with its name and icon, and the firewall's per-apprestrictions (`lpk:mail`, …) apply to it ([docs/PRIVACY.md](docs/PRIVACY.md#system-apps-in-their-own-process-082)).+- **LordOS checks its own code before running it.** Every bundle LordOS runs as its own code — the+ themes with the shell and every native app, the login screen, the app host of isolated apps and+ the system apps that run as their own process — is listed with its SHA-256 in+ `/usr/lib/lordos/code-manifest.json`, signed with the LordOS release key (Ed25519).+ lord-server verifies the signature with the public key compiled in, and the hash of each bundle+ as it loads it, from the same read (no window to swap the file). A bundle that doesn't match is+ not run: the desktop falls back to another theme and shows "This LordOS component was modified and+ was not loaded"; with nothing left to load (or at the login screen) a built-in recovery screen+ explains it and how to repair it, never a blank screen. It protects against changes by non-root+ processes and offline modification; root can still replace lord-server itself, which phase 3+ (fs-verity, A/B images) will cover. Cost on a session start: about 7 ms on a Raspberry Pi 5,+ 18–34 ms on a 1.8 GHz Xeon VM+ ([docs/SIGNING.md](docs/SIGNING.md#verified-system-code-082)).+- **System apps can't be removed.** Store → Installed shows "System app — part of LordOS" instead+ of Remove for the apps that come with LordOS, and the `lordos` package is marked `Protected` so the+ Store's package engine refuses to remove it.-### Changed--- Isolated apps start faster: the app host is compiled to bytecode once per session, so an app's- JavaScript loads in ~23 ms instead of ~110 ms (Mail's window: ~145 ms from the click to its first- frame on a 1.8 GHz test machine).-- The Dock's quick actions and **New window** now work for the apps that run in their own process;- Passwords stays a single window.-- An isolated app's process is named after the app (`mail`), not `exe`, in `ps` and Monitor.--### Fixed+### Known issues and limitations-- Isolated apps showed times in UTC instead of the local time zone.-- Trusting a self-signed certificate for an SMTP server on port 465 pinned it as the IMAP server's,- so sending kept failing.+- **City names on the map.** Debian 13 only ships country-level IP databases (`geoip-database`) and+ LordOS's own is country-level too, so labels stay countries; no large download was added.## [0.8.1-beta] - 2026-10-19diff --git a/docs/UPDATES.md b/docs/UPDATES.mdindex 88a2ba5..d860737 100644--- a/docs/UPDATES.md+++ b/docs/UPDATES.md@@ -195,6 +195,7 @@ Today's migrations:|---|---|| `001-0.8.1-network-permissions` | Enables `lord-netperm.service` (per-app network permissions) where `lordos.service` is enabled. The ISO, the Pi image and `install.sh` already did; a system set up with `apt` alone had it off. Runs once: disabling it later sticks. || `002-0.8.1-root-ssh-keys` | 0.8.1 adds `PermitRootLogin no` (`/etc/ssh/sshd_config.d/10-lordos.conf`). On an **upgrade** from 0.8.0 with SSH installed and keys in `/root/.ssh/authorized_keys` (a VPS run as root), it writes `09-lordos-root-keys.conf` with `PermitRootLogin prohibit-password`, so root keeps logging in with keys (never passwords) instead of being locked out at the next restart. New installs never get it; delete the file to apply LordOS's default. |+| `003-0.8.2-drivetemp` | 0.8.2 ships `/usr/lib/modules-load.d/lordos-drivetemp.conf` (SATA disk temperatures in Monitor → Disks, read at boot). On a running system it loads `drivetemp` once, so the temperatures show without a restart. Does nothing without systemd (an image being built) or where the kernel has no `drivetemp`. |**Settings migrations** (each user), in `sdk/settings.js`: `MIGRATIONS` is a list of`[schema, (settings) => newSettings]` applied in order when the session loadsdiff --git a/docs/VM-SETUP.md b/docs/VM-SETUP.mdindex 80437f5..0c4a111 100644--- a/docs/VM-SETUP.md+++ b/docs/VM-SETUP.md@@ -1160,7 +1160,7 @@ disk, boot, network and LordOS installation were not touched.only while it runs; QEMU uses user-mode networking.- **Left behind:** the packages above and `/var/tmp/lordos-immutable` (~5 GB; delete it to free thespace). Nothing else changed.-## Step 29 — New wallpapers (VM 123 `lordos-monitor`, October 19)+## Step 30 — New wallpapers (VM 123 `lordos-monitor`, October 19)Tree in `~/LordOS-wp`, built there (`make -C server -j4`, `make -C server test`: 23 passed,3 skipped). Nothing was installed with apt.@@ -1178,7 +1178,7 @@ Tree in `~/LordOS-wp`, built there (`make -C server -j4`, `make -C server test`:removed to show the greeter and then autologin again; `/etc/lordos/session.conf` wasn't changed.- **Screenshots** with `screendump` from the Proxmox host, the pointer with`lord-qmp-input.py 123 1280 800`. eth0 and the VM's network weren't touched.-## Step 29 — Disk temperatures and SMART with smartmontools (VM 119 `lordos-spot`, October 19)+## Step 31 — Disk temperatures and SMART with smartmontools (VM 119 `lordos-spot`, October 19)See `MONITOR.md` ("Disk temperature and health") and `SYSTEM.md` ("SMART with smartmontools").@@ -1196,7 +1196,7 @@ See `MONITOR.md` ("Disk temperature and health") and `SYSTEM.md` ("SMART with sm`server/tests/smart/` were captured with a `smartctl` unpacked into `/tmp/smx` (`apt-get download`+ `dpkg -x`, never installed).- Nothing else changed: no Proxmox setting, no network setting.-## Step 29 — Monitor → Network: per-destination switches, traffic history, several damaged rectangles (VM 119 `lordos-spot`, October 19)+## Step 32 — Monitor → Network: per-destination switches, traffic history, several damaged rectangles (VM 119 `lordos-spot`, October 19)See `MONITOR.md` ("Per-destination switches", "Traffic history", "0.8.2: several damagedrectangles"). On VM 119 (172.17.0.54), built in its own folders (`~/LordOS-monred`, plus@@ -1223,7 +1223,7 @@ the end.- **Screenshots** with `screendump` from the Proxmox host; pointer and keys with`lord-qmp-input.py 119 1280 800` and `qm monitor 119` `sendkey`.- Nothing in the network configuration was touched (`eth0` keeps 172.17.0.54).-## Step 29 — Mail, Calendar, Contacts and Reminders in their own process (VM 118 `lordos-notes`, October 19)+## Step 33 — Mail, Calendar, Contacts and Reminders in their own process (VM 118 `lordos-notes`, October 19)See `PRIVACY.md` ("System apps in their own process"). On VM 118 (172.17.0.53), tree in`~/LordOS-inmut2`, built there and installed into `/usr/local/lib/lordos` (`lord-server`,