ObliviOS Developer portal Project site

Home / Decisions / ADR-185

Accept the Passwords app design (2026-10-20-password-manager-design.md) as the default autofill and credential provider of FreeholdOS.

Accepted, recorded 20 October 2026.

Decision
ADR-185
Date
2026-10-20
Status
AcceptedAccepted
Part
Passwords
Mentioned by
ADR-190, ADR-191, ADR-192, ADR-193, ADR-197, ADR-202

1Decision

Accept the Passwords app design (2026-10-20-password-manager-design.md) as the default autofill and credential provider of FreeholdOS. (1) The vault is local only: no account, no server, no sync (this makes the optional end-to-end sync of section 22 of the requirements a non-goal), no network permission; the only way out is one encrypted export file in an open format under its own passphrase, and the generic Backup component never carries the vault.

(2) Key hierarchy: a random 256-bit vault key in one sealed file; a passphrase wrapper from Argon2id mixed with a non-exportable hardware secret in the Keystore; a biometric wrapper that needs a fresh strong-biometric authentication for every use, with no screen-lock fallback; the passphrase is required after a restart, a biometric enrollment change, five failed biometric attempts and 7 days; the vault locks after one minute in the background and when the device locks; no recovery and no master key.

(3) While the vault is locked the keyboard chip appears only on sites or apps with an account, found through an HMAC index of exact registrable domains and package names under a separate Keystore key, with the residual leaks of section 4.1 of the design accepted and no index padding. (4) The app is Jetpack Compose with Material 3 and the cryptographic core is Rust with vendored RustCrypto crates, gated by the feasibility task of the plan.

(5) Logos come from the installed app icon, a bundled icon pack and a generated pattern as fallback; nothing is fetched. (6) Version 1 holds passwords only, each with a notes field. The inline chips in the keyboard strip need inline-suggestion support in LatinIME and are a second plan.

2Why and evidence

The owner decided the points above on 2026-10-20 or left them to the design (chip rules, Checkup scope, the detail items, toolkit and core language). Prior art: the requirements ask for hardware-backed keys, per-world vaults and biometric convenience with a passphrase fallback and have no key design; the tree has the autofill and credential provider services, a combined Settings picker and two opt-ins for inline suggestions, and GuardianApp already builds Compose and Material 3.

3Consequences

The plan 2026-10-20-password-manager.md implements it; the app lives in freeholdos-platform/passwords/ and the core in freeholdos-services/vault-core/. A bundled third-party icon set needs a trademark review before it ships. Without inline support in the keyboard, a keyboard other than the restyled LatinIME shows the system dropdown. Downloads of the vendored crates, builds and device tests need separate owner approval.

4Review when

The feasibility gate (Task 1) shows that the vendored crypto does not build with the AOSP Rust; lynx or stallion lacks strong biometrics or hardware-backed keys; Keystore keys turn out to expire on an update; the autofill framework lets the requesting app see whether a chip was offered; the trademark review refuses the icon set; the dropdown fallback proves unacceptable and the chips cannot be built.

Read from docs/governance/decision-log.md, entry ADR-185.