ObliviOS Developer portal Project site

Home / Decisions / ADR-145

Duress Unlock gets a Settings screen to set up, change and remove the decoy.

Accepted, recorded 7 October 2026.

Decision
ADR-145
Date
2026-10-07
Status
AcceptedAccepted
Part
Duress Unlock
Mentions
ADR-038
Mentioned by
ADR-147, ADR-210

1Decision

Duress Unlock gets a Settings screen to set up, change and remove the decoy (design): a second row "Duress Unlock" below "Duress password" on the Device unlock page, available for the system user only, with a PIN-only decoy credential and a PIN screen lock.

Patches in credential/duress-unlock-decoy: frameworks-base/0012 (ILockSettings#isDuressWipeCredential(ownerCredential, candidate), appended last, write permission and owner credential required, no wipe and no routing), packages-apps-settings/0003 (the set-up flow and its JVM tests) and packages-apps-settings/0004 (the screens, the row, strings, manifest).

It does not change routing, the keyguard hook, quiescing or the user switch, and it leaves the upstream wipe feature untouched (ADR-038).

2Why and evidence

Owner decision 2026-10-07 (chat): approved the design, the framework method over a warning-only alternative, PIN-only until a password is built, and one independent code review before any build. Until now the decoy was provisioned only with shell commands. Settings cannot tell whether a decoy PIN equals the wipe PIN, and such a PIN would silently disable the wipe because decoy routing replaces the verification response before the wipe hook sees it; asking through checkCredential would itself start the wipe or the switch. The new method answers it with the check the wipe hook already uses. The review of 2026-10-07 found no blocking defect and its fixes are in the patches.

3Consequences

The method says whether a guess is the wipe PIN, with no throttle, to a caller that holds the owner credential and the write permission; that caller can already overwrite the wipe PIN, so the gain is small. A decoy PIN of another length than the lock PIN is refused while Auto confirm unlock is on. A process kill during the set-up leaves a decoy user without a registration, which Change PIN completes and Remove deletes.

Setting a wipe PIN equal to an existing decoy PIN is still not prevented (open work in status.md). The patches are landed with git am on frameworks/base sovereignos-2026091900-r2 and packages/apps/Settings sovereignos-2026091900; they are compiled into the lynx userdebug image 2026100226 (DUR-002) and not run on a device.

4Review when

Accepted fully when rows DUR-001 to DUR-013 of the validation matrix have evidence or the owner waives them; a row that fails on lynx reopens the design.

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