NanumOS

Login and the vault — one password

What it is

NanumOS has one password. The login password you type at start is the master password of the vault (where passwords are kept). It is like one front-door key that also opens the drawers inside (the keys your apps use).

What to do now: if you have no vault yet, make one in the Vault app. Its master password becomes your login password.

How to use it

  1. The first time — if a vault exists but was never opened on this device, "Open the vault?" shows once when an app first needs a key (or open it once in the Vault app). Type the vault's master password.
  2. After that — with automatic login on, the desktop comes up at once and the assistant answers with the paid model right away. No window asks anything.
  3. An app needs a key while the vault is locked — "Open the vault?" appears right there. Type the password and what you were doing goes on. You never have to open the Vault app first.
  4. The Vault app — the list shows as soon as you open it. To show or copy a password it asks the master once; after 10 minutes without use the values are hidden again. Lock (Ctrl+L) only hides the values — the apps keep their keys.
  5. Settings › General › Automatic login — on: nothing asked at start (the default). Off: the vault's master is asked at start and to unlock the screen.
  6. Other apps and plugins (not made by us) show an [Allow] card the first time they want a key. "Always Allow" is remembered; remove it in Settings › General › Passwords › Access….

How it works

Technical details
  • Stored: /etc/vault/login (auto or password), /etc/vault/session (the keyring as the kernel holds it — entries, transformed key, path — sealed with ChaCha20-Poly1305), /etc/vault/device (the sealing key, 32 random bytes). Both root 0600 and kernel-only: a program, root or a desktop app trying to read them is refused; only the persist save carries them. No key value is ever returned to a program.
  • At start the desktop (or an app's first key request) opens this session inside the kernel — no Argon2, no file parsing. vault unlock --auto only asks the kernel to do it and gets the entry count. vault login password overwrites both files, then removes them. A changed master is sealed again at the next unlock.
  • Trade-off (read this): while automatic login is on, whoever has this device's whole storage disk can open the vault — the sealing key is on the same disk (the same level as keeping a Wi-Fi key). Disk copies and backups too. Turn automatic login off on a shared or carried device.
  • The kept session is the vault as it was then: changes from other devices come in through zcloud the next time the master is typed or an entry is changed.
  • Two levels: the kernel keyring (used by the apps) is wiped only by vault lock or a restart; "values shown" (the Vault app showing and copying values) closes after 10 idle minutes, on Lock, and on the Vault app's Lock.
  • No question for: zeus (the assistant, in the Terminal and Zeus Studio) and Mail — only when the host asked for is the entry URL's host (or a name under it). The log says allowed (built-in); no grant is written. Scripts (micropython …), plugins, ssh and agent sessions are asked as before.
  • Locked and a key wanted: while the broker call waits (EAGAIN) the desktop shows the password sheet; once open the same call goes on (within 60 s). Without a desktop it is refused as before (exit 5).
  • State: vault report — state, passwords, login, session, grants, asked (questions this boot), builtin, auto_logins. No names, hosts or values. vault status says the same in words.
  • Log lines go to serial, dmesg and /var/log/messages only (not the Terminal).

NanumOS 0.1.8349 · 2026-11-16