← All documentation

Security

How AOS keeps you safe

A read-only core that checks itself, Secure Boot, a home encrypted for each account, a firewall that is closed by default, and nothing sent about you.

AOS is built so that the safe way is the only way. Most of what follows needs nothing from you: it is how the system is put together.

A core that cannot be changed

The operating system itself is one compressed image, mounted read-only. Every block is checked against a hash tree (dm-verity) as it is read, and the root of that tree is part of the signed kernel image. If anything on the disk was tampered with, that copy of the system does not boot.

Nothing a program does to the system survives a restart, and no program, not even an administrator’s, can quietly patch the core.

Two copies, so updates can’t break it

There are two system slots. An update is written into the slot you are not using, and the next boot tries it on trial, with three tries. When the desktop comes up, the update is confirmed. If it doesn’t, the machine goes back to the slot that worked. See Install, updates and recovery.

Secure Boot from the start

The boot chain is a Microsoft-signed shim, then systemd-boot, then one signed kernel image per slot. You enrol the AOS key once, during installation, in the blue MokManager screen. After that every kernel and every kernel module must carry a valid signature.

Encryption

  • Every account’s home is its own encrypted vault (systemd-homed, LUKS2). It is unlocked by your password when you log in and locked when your last session ends. Another account on the same machine cannot read it.
  • A recovery key is shown once at first boot. Write it down: it is the only way in if you forget your password.
  • Whole-disk encryption is an option in the installer (“Encrypt the disk”). With a TPM, the machine unlocks the disk by itself as long as the boot chain is the one it trusts.

Apps in a sandbox, and no root

Two rules do most of the work:

  • Apps live in a sandbox. A program from Software sees its own folder and what you allowed, not your whole home.
  • There is no root account and no sudo. Every change to the system goes through one small service, one checked action at a time.

A firewall that is closed

Nothing from the network can reach your machine unless you asked for it. The firewall drops everything that isn’t a reply, apart from DHCP and ping, the ports an app declared and you switched on, and SSH, which is off until you turn it on in Settings → Network. While SSH is on, the bar shows SSH open in red.

Signed software only

Every package index is signed, and apm checks every package against it. The first time you add a repository, apm remembers its key (trust on first use). A later index signed with a different key is refused. Only the official AOS repository may run anything as root during an install. Everything else is labelled not part of AOS in Software.

Privacy: nothing about you leaves on its own

AOS has no telemetry, no accounts and no crash uploads. The only things that go out are:

What When To
Update and package index check Daily, and when you press “Look for updates” GitHub
Package downloads When you install or update GitHub, or the vendor of a third-party app
Time sync In the background Netnod, then pool.ntp.org
Weather Only after you pick a place Open-Meteo
Firmware updates Only when you ask LVFS (fwupd)
Bug reports Only when you send one Adelon

None of these carry an identifier for your machine or your account.

Known limits

AOS is an alpha, and the parts still being hardened are written down openly. For example, there is no MAC policy (AppArmor or SELinux) yet, and whole-disk encryption is off unless you choose it. See the security notes on GitHub.