- Decision
- ADR-067
- Date
- 2026-08-30
- Status
- AcceptedAccepted
- Part
- Duress Unlock
- Mentions
- ADR-063, ADR-064, ADR-065, ADR-066
- Mentioned by
- ADR-087, ADR-213
1Decision
Commission and record an exhaustive, owner-requested audit for every remaining decoy identity-leak surface, on the owner's explicit assessment (after ADR-066) that on the order of 15 comparable leaks likely still existed unfound. Full findings: docs/superpowers/specs/2026-08-30-duress-decoy-remaining-leaks-audit.md. Fix in the audit's own recommended priority order, one item at a time, each through the established local-first patch/build/validate discipline.
2Why and evidence
A read-only source audit across frameworks/base, packages/apps/Settings, packages/apps/Multiuser, packages/apps/Launcher3, every other packages/apps/* in the tree, and vendor/aegisos/guardian found 21 distinct candidate surfaces — matching and somewhat exceeding the owner's own estimate.
Three are Critical and previously undocumented: a legacy power-menu fallback (LegacyGlobalActions.java:552) that renders every real user's name directly on the lock screen via raw getUsers(), entirely outside getUsersForUiDisplay, triggered whenever SystemUI fails to respond to a power-menu request within 5 seconds (a live fallback path, not dead code); Settings' own "Users" management screen (UserSettings.java:1348), reachable from a non-admin decoy since it is gated only on device multi-user support, not admin status; and storage move/migrate credential dialogs that template a real user's name into a system unlock dialog.
Four more are the same already-fixed bug class recurring at sibling call sites the original migration missed (uninstall-dialog text via the unmigrated UserManager#getUserCount(), a Wi-Fi "shared" badge, a Wi-Fi "forget shared network" dialog, and a factory-reset "other users present" warning).
One is a currently-dormant landmine: the lock-screen status-bar multi-user icon (KeyguardStatusBarView's mMultiUserAvatar, directly observed on the physical device during this session) is masked today only as an accidental side effect of the decoy's own default restriction set, not because its underlying gate (UserManagerService#areThereMultipleUiSwitchableUsers()) was ever fixed — it would become a live leak the moment an unrelated restriction default changes.
One (the Multiuser widget's own data layer, UsersRepository.kt) loads every real user's name/avatar unfiltered into memory, currently withheld from rendering only by an incidental filter elsewhere in the same widget, not by design. One (Guardian's AppOps watcher) is flagged but not confirmable from this repository's source alone, since the relevant label-resolution code lives in the compiled aegisos-services artifact.
Three items were explicitly left as low-confidence, needing further tracing before a responsible fix/no-fix call, rather than being fixed or dismissed blind.
A substantial confirmed-safe list is recorded too, including surfaces specifically checked because a wrongly-scoped version would have been severe (the media-projection screen-share app selector, the bouncer's own user-switcher dropdown, and the real, non-legacy GlobalActionsDialogLite power menu, all confirmed to key correctly off the actual current user).
3Consequences
The audit document is the authoritative source for per-item detail; this entry does not restate it. The owner chose to fix items one at a time in the audit's own recommended order (Critical items 1-3 first, then the four sibling-pattern fixes, then the dormant status-bar icon and the widget's defense-in-depth gap, then Guardian pending further evidence, with the three low-confidence items deferred until traced further) rather than a single grouped patch or a fresh full design/plan cycle — each fix follows the same local-first worktree/patch/build/validate discipline already established for ADR-065/066.
4Review when
Track completion of each of the 21 items against the audit document as fixes land; a future closing entry (matching this plan's own ADR-064/ADR-063 precedent for "don't claim fully closed until a final independent pass confirms it") should re-review the whole list once the recommended-priority items are done, rather than assuming line-item completion alone proves the session is finally leak-free.
Read from docs/governance/decision-log.md, entry ADR-067.