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
Docs: remote login (SSH) in Settings → Sharing
Federico Pereira7767440b049b
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex e7aa47b..d8e61c8 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -10,7 +10,15 @@ of the matching [GitHub release](https://github.com/lordbasex/LordOS/releases),## [Unreleased]-Nothing yet.+### Added++- **Settings → Sharing → Remote login (SSH).** A new switch, off by default on every install,+ turns the standard SSH server on and off for good (`systemctl enable --now` / `disable --now`).+ The first time, it installs `openssh-server` through the package engine (the Store's path). The+ page shows `ssh <user>@<address>` for this computer and its ED25519 host key fingerprint, and+ lets you allow all users or only administrators. Root never logs in (`PermitRootLogin no` in a+ drop-in shipped by the `lordos` package). The Raspberry Pi image's `ssh` switch file keeps+ working and shows up as on ([docs/REMOTE.md](docs/REMOTE.md#remote-login-ssh)).## [0.8.0-beta] - 2026-10-18diff --git a/docs/REMOTE.md b/docs/REMOTE.mdindex f939fe1..5071b2c 100644--- a/docs/REMOTE.md+++ b/docs/REMOTE.md@@ -16,6 +16,8 @@ The port is **5673**, which spells "LORD" on a phone keypad.before switching users).- **It's off by default.** It's turned on and off in Settings → Sharing → «Remote Desktop», as onpopular desktop systems.+- **Terminal access** (SSH) is a separate switch on the same page: see+ [Remote login (SSH)](#remote-login-ssh).@@ -156,6 +158,97 @@ session's PipeWire:for it.- **Dependency:** libopus, only in lord-sessiond.+## Remote login (SSH)++Settings → Sharing also has **«Remote login (SSH)»**: other computers open a terminal on this one+with any SSH client (`ssh <user>@<address>`), with a user and password of the machine. It's the+standard OpenSSH server (`openssh-server`), not something of our own.++++- **It's off by default on every install:** the live ISO, a disk installed from it, the Raspberry+ Pi image and the Debian installer. The ISO and the installed system don't even ship+ `openssh-server`; the Pi image ships it disabled. The switch shows the real state: whether+ `ssh.service` (or `ssh.socket`) is enabled to start at boot, and whether `sshd` is running.+- **Turning it on:**+ 1. If `openssh-server` isn't installed, Settings installs it with the package engine's own+ action, `pkg-install openssh-server openssh-sftp-server` (the Store's path, `server/src/pkg`+ and `dpkg`; `openssh-sftp-server` is a Recommends the engine skips, and `scp`/`sftp` need+ it). With no package lists yet (a fresh install) it runs `pkg-update` once first. It needs+ the internet.+ 2. Then `ssh-set on`: it creates the host keys if missing (`ssh-keygen -A`), checks the+ configuration (`sshd -t`) and runs `systemctl enable --now ssh.service`. It stays on across+ reboots.+- **Turning it off:** `ssh-set off` runs `systemctl disable --now ssh.service ssh.socket`. The+ package stays installed. Sessions already open aren't cut (Debian's unit uses+ `KillMode=process`); new ones are refused and port 22 closes, also after a reboot.+- **How to connect:** when it's on, the page shows `ssh <your user>@<address>` for each LAN IPv4+ address and for the machine name, and the **ED25519 host key fingerprint** (`SHA256:…`, computed+ by `lord-server` from `/etc/ssh/ssh_host_ed25519_key.pub`, the same as+ `ssh-keygen -lf /etc/ssh/ssh_host_ed25519_key.pub`). Compare it with the one `ssh` shows the+ first time it connects.+- **Who can log in:** all users with a password (the default), or **only administrators**+ (`ssh-allow admins` writes `/etc/ssh/sshd_config.d/11-lordos-allow.conf` with+ `AllowGroups sudo admin wheel`, checks it with `sshd -t` and reloads the server; `ssh-allow all`+ removes it). **Root never logs in.**+- **Raspberry Pi:** the image's `ssh` switch file on the boot partition keeps working+ ([RASPBERRY.md](RASPBERRY.md)): it enables `ssh.service`, and the Settings switch shows it on.+- **Debian installer** (`install.sh`): it never touches an existing SSH server (on a server or VPS+ it may be how you are connected); it only reports its state at the end.++++### Safe defaults++The `lordos` package ships `/etc/ssh/sshd_config.d/10-lordos.conf`, read only once+`openssh-server` is installed. Debian's `sshd_config` includes that folder at the top and `sshd`+keeps the first value it reads, so it wins over the rest:++- `PermitRootLogin no`.+- Password logins stay on, because people expect them. **Key logins are safer**: copy your key+ with `ssh-copy-id <user>@<address>` and, once it works, you may add a file in that folder with+ `PasswordAuthentication no`.+- Nothing else is changed: Debian's defaults (key types, ciphers, `MaxAuthTries`) stay.++### Privileges++The privileged part is two closed actions of the admin helper (`server/src/remote/ssh_admin.c`,+`SSH_ADMIN_ACTIONS` in `admin.c`), only for administrators (sudo, admin or wheel), like the+`remote-*` actions:++| Action | Argument | What it runs (fixed paths) |+|-------------------------|-------------------|--------------------------------------------------------------------------|+| `ssh-set` | `on` or `off` | `ssh-keygen -A` if there's no host key, `sshd -t`, `systemctl enable --now` / `disable --now` |+| `ssh-allow` | `all` or `admins` | writes or removes the fixed `AllowGroups` drop-in, `sshd -t`, `systemctl try-reload-or-restart` |++Nothing the user types reaches a command line or sshd's configuration, and no package is installed+by these actions: that stays in the package engine. `lord-server` only reads the state+(`lord.ssh.status()` in `server/src/ui/js_sys.c`: the unit files, `/proc/*/comm` for a root+`sshd`, the drop-in and the public host key), and doesn't run anything.++### Firewall++Nothing to open. `lord-netperm`'s per-app rules apply to programs started from a LordOS session+(they live in its cgroup tree); `sshd` is a system service in `system.slice/ssh.service`, so the+rules never block it, and LordOS adds no system-wide packet filter. If you run your own (nftables,+a router), allow TCP port 22 from the local network only. As with remote desktop, to use it from+the internet, use a VPN instead of opening the port.++### Tested (VM 122, Debian 13, 0.8.1 development build)++- With `openssh-server` purged, the switch was off and port 22 closed. Turning it on installed+ `openssh-server` and `openssh-sftp-server` through `pkg-install` (about 20 s), created new host+ keys and started the server; the fingerprint on the page matched+ `ssh-keygen -lf /etc/ssh/ssh_host_ed25519_key.pub`.+- From another machine: key login, password login and `scp` worked; `root` was refused+ (`sshd -T`: `permitrootlogin no`, `passwordauthentication yes`).+- «Only administrators»: `bob` (not in sudo) was refused («none of user's groups are listed in+ AllowGroups»), `lord` logged in. Back to «All users» removed the drop-in.+- Reboot with it on: still enabled and listening. Turned off: `ssh.service` disabled and+ inactive, port 22 closed, and still closed after another reboot.+- A standard user (lord taken out of `sudo` for the test): the page shows the administrator note+ and the switch does nothing; the server stayed off.+## Files| Path | What it is |@@ -164,6 +257,8 @@ session's PipeWire:| `server/src/remote/enc.c` | PNG/JPEG (stb_image_write, vendored in third_party/stb) || `server/src/remote/login.html`, `client.html` | pages (embedded in the binary) || `server/src/remote/remote_admin.c` | `remote-*` actions |+| `server/src/remote/ssh_admin.c` | `ssh-*` actions (remote login) |+| `tools/iso/rootfs/etc/ssh/sshd_config.d/10-lordos.conf` | sshd defaults shipped by the `lordos` package || `apps/settings/Sharing.jsx`, `sdk/remote.js` | Settings → Sharing and the notice on the monitor || `/etc/lordos/remote/` | `config`, `cert.pem`, `key.pem`, `fingerprint` |@@ -174,3 +269,5 @@ session's PipeWire:- - - +- +- diff --git a/docs/VM-SETUP.md b/docs/VM-SETUP.mdindex aba428a..070755f 100644--- a/docs/VM-SETUP.md+++ b/docs/VM-SETUP.md@@ -1106,3 +1106,21 @@ See `FIREWALL.md`, "Linux apps". Tree in `~/LordOS-fwlinux`, built there (`make- **Scripts:** `server/tests/fwlinux/{devices,bluetooth,files,notify,mic,screen}.sh`, run as `lord`.They build app scopes by hand as root under `lordos-session-1000` and put `firewall.json` backat the end. Nothing in the network configuration was touched.++## Step 27 — Remote login (SSH) in Settings → Sharing (VM 122 `lordos-sandbox`, October 18)++See `REMOTE.md`, "Remote login (SSH)". Tree in `~/LordOS-ssh` (sent with `tar`), only+`make -C server build/lord-server`; that `lord-server`, the three theme bundles, `app-host` and+`assets/locales` were installed over `/usr/lib/lordos` after saving the previous ones.++- **Packages:** `openssh-server` and `openssh-sftp-server` were purged with `apt-get` (test setup:+ a system without the SSH server, driven through `qm guest exec 122`) and installed again by the+ Settings switch through the package engine (`pkg-install`), same version+ (`1:10.0p1-7+deb13u4`).+- **Changes undone at the end:** the previous `/etc/ssh` (host keys and the cloud image's+ `sshd_config` with `PasswordAuthentication no`) was restored from a backup, both LordOS drop-ins+ were removed and `ssh.service` was enabled again, so other agents' SSH access and known host+ keys are unchanged. `lord` was taken out of `sudo` for the standard-user test and put back. The+ saved `lord-server`, themes and assets were restored and `~/LordOS-ssh` deleted.+- **Side effects:** the VM was rebooted twice (the reboot tests), which ended `bob`'s background+ session; `lord` ends at the login screen. Nothing in the network configuration was touched.diff --git a/docs/settings-sharing-ssh-dark.png b/docs/settings-sharing-ssh-dark.pngnew file mode 100644index 0000000..1f0b631Binary files /dev/null and b/docs/settings-sharing-ssh-dark.png differdiff --git a/docs/settings-sharing-ssh-light.png b/docs/settings-sharing-ssh-light.pngnew file mode 100644index 0000000..d1a04b5Binary files /dev/null and b/docs/settings-sharing-ssh-light.png differdiff --git a/docs/settings-sharing-ssh-off-dark.png b/docs/settings-sharing-ssh-off-dark.pngnew file mode 100644index 0000000..99d9986Binary files /dev/null and b/docs/settings-sharing-ssh-off-dark.png differdiff --git a/docs/settings-sharing-ssh-off-light.png b/docs/settings-sharing-ssh-off-light.pngnew file mode 100644index 0000000..f8a8a33Binary files /dev/null and b/docs/settings-sharing-ssh-off-light.png differdiff --git a/web/content/faq/faq.json b/web/content/faq/faq.jsonindex d676bb8..c5b09c6 100644--- a/web/content/faq/faq.json+++ b/web/content/faq/faq.json@@ -498,9 +498,9 @@"pt": "O desktop remoto vem ligado?"},"a": {- "en": "No. It's off by default and port 5673 stays closed until you turn it on in Settings → Sharing. Then you open `https://<the computer's address>:5673` in a browser on your local network and log in with your account; the connection is encrypted with TLS. To reach it from the internet, use a VPN rather than opening the port.",- "es": "No. Viene apagado y el puerto 5673 queda cerrado hasta que lo encendés en Ajustes → Compartir. Después abrís `https://<la dirección del equipo>:5673` en un navegador de tu red local y entrás con tu cuenta; la conexión va cifrada con TLS. Para llegar desde internet, usá una VPN en vez de abrir el puerto.",- "pt": "Não. Ele vem desligado e a porta 5673 fica fechada até você ligá-lo em Ajustes → Compartilhar. Depois você abre `https://<o endereço do computador>:5673` num navegador da sua rede local e entra com sua conta; a conexão é criptografada com TLS. Para acessar pela internet, use uma VPN em vez de abrir a porta."+ "en": "No. It's off by default and port 5673 stays closed until you turn it on in Settings → Sharing. Then you open `https://<the computer's address>:5673` in a browser on your local network and log in with your account; the connection is encrypted with TLS. To reach it from the internet, use a VPN rather than opening the port. Remote login over SSH (Settings → Sharing → Remote login) is a separate switch, also off by default; the first time you turn it on it installs the SSH server.",+ "es": "No. Viene apagado y el puerto 5673 queda cerrado hasta que lo encendés en Ajustes → Compartir. Después abrís `https://<la dirección del equipo>:5673` en un navegador de tu red local y entrás con tu cuenta; la conexión va cifrada con TLS. Para llegar desde internet, usá una VPN en vez de abrir el puerto. El inicio de sesión remoto por SSH (Ajustes → Compartir → Inicio de sesión remoto) es otro interruptor, también apagado de fábrica; la primera vez que lo encendés instala el servidor SSH.",+ "pt": "Não. Ele vem desligado e a porta 5673 fica fechada até você ligá-lo em Ajustes → Compartilhar. Depois você abre `https://<o endereço do computador>:5673` num navegador da sua rede local e entra com sua conta; a conexão é criptografada com TLS. Para acessar pela internet, use uma VPN em vez de abrir a porta. O login remoto por SSH (Ajustes → Compartilhar → Login remoto) é outro interruptor, também desligado de fábrica; na primeira vez que você o liga, ele instala o servidor SSH."}},{