Security
Root and administration
There is no sudo on AOS and no account can become root. Changes to the system go through one small service, one checked action at a time.
On most Linux systems an administrator types sudo and can then do anything, and so can any program or script that gets hold of that moment. AOS takes that away. No account can become root. There is no sudo, no su, and the root account has no password.
Type sudo in the Terminal and AOS tells you so, and where to go instead.
How admin tasks work: aos-rootd
Every change to the system goes through aos-rootd, a small service that runs as root and offers a fixed list of actions: join this Wi-Fi network, add this user, install this package. It has no “run this command” action. Each action checks its arguments itself before doing anything.
Who may use it:
| Who | What they can do |
|---|---|
| Administrators (the account made at first boot, and anyone you make an admin in Settings → Users) | Look at status without a password. Make changes after giving their own password, which stays valid for 15 minutes from the last change |
| Other accounts | Nothing that changes the system. They get “Not an administrator” |
| Sandboxed apps | Nothing. They cannot even see the service |
| On the live USB stick | Any admin acts without a password, since whoever holds the stick owns it |
Every call and every refusal is written to the system log with who asked and what for. Your password and the arguments are never logged.
Doing admin things
In Settings, a change that needs an administrator shows a bar at the bottom: “This change needs your password.” Type it once, and for the next 15 minutes other changes go straight through.
| Where | What needs an admin |
|---|---|
| Settings → Network | Joining and forgetting Wi-Fi, enterprise Wi-Fi, VPN, remote login (SSH), app ports |
| Settings → Users | Adding and removing accounts, making someone an admin, other people’s passwords, kiosk mode |
| Settings → Date & Time, Keyboard | Time zone and time sync, the system keyboard layout and language |
| Settings → Power | Lid behaviour and hibernation |
| Settings → Printers | Adding and removing printers |
| Settings → About | Computer name, TPM unlock, firmware updates, report consent |
| Software | Installing, removing and updating, the third-party repository, adding repositories, the update channel |
| Disks | Formatting a drive (never the one AOS runs from) |
In the Terminal:
aos-root unlock # asks your password, opens the 15 minutes
apm install mozilla/firefox # re-runs itself through aos-root when needed
aos-root apm upgrade # apm on the system, explicitly
On AOS 0.4.70 and earlier, aos-root unlock hung without a prompt, and aos-root apm … answered “Wrong password” without asking. Update to 0.4.71, or unlock in Settings first: the 15 minutes count for the Terminal too.
Anything else that aos-rootd offers can be called directly with busctl call org.aos.Root /org/aos/Root org.aos.Root <Method> …. Helper scripts such as aos-wifi or aos-tpm print the right Settings page or command when they need root.
What you can do without root
Quite a lot, as any user, with no password:
- Everything in your own home: files, settings, appearance, sound, displays, mouse, accessibility, default apps.
- Pair Bluetooth devices, lock the screen, suspend.
- Plug in USB sticks and drives. They mount by themselves under
/run/media. - Back up your home, encrypted, to a drive (Settings → Backup).
- Change any app’s permissions in Software.
- Run your own background services with
systemctl --user, for examplessh-agent. - Read your own logs with
journalctl --user. - Install a package just for yourself:
apm --user install ./tool.apkggoes into~/.apmand needs no password. - See your own processes. Other accounts’ processes are hidden from you.
Joining a new Wi-Fi network does need an administrator.
What if something isn’t covered?
Then it can’t be done on an installed machine. There is no back door into a root shell: that is the point. Things that need root in other systems either have an action in aos-rootd, or they are missing until one is added. If you hit one, report it.
For repairs, the live USB stick gives you a root console (Ctrl+Alt+F2). An installed machine never does.