ObliviOS Developer portal Project site

Home / Decisions / ADR-072

Consolidated m systemimage build confirming all ten original audit fixes compile together, followed by a physical lynx hardware build/sign/flash of all eleven fixes…

Accepted, recorded 3 September 2026.

Decision
ADR-072
Date
2026-09-03
Status
AcceptedAccepted, partial
Mentions
ADR-047, ADR-049, ADR-062, ADR-066, ADR-071
Mentioned by
ADR-073, ADR-079, ADR-087, ADR-092

1Decision

Consolidated m systemimage build confirming all ten original audit fixes compile together, followed by a physical lynx hardware build/sign/flash of all eleven fixes (the ten plus ADR-071's packages-apps-settings 0007), and the first real dynamic (not just compile-time) validation of any of this audit's fixes.

2Why and evidence

m systemimage (out-preflight, sdk_phone64_x86_64-cp2a-userdebug): Build Succeeded: 3658 steps, 54m13s — all ten original fixes compile together cleanly.

The physical candidate: lunch lynx-cur-userdebug, OFFICIAL_BUILD=true independently confirmed via direct /proc/<pid>/environ inspection of the running build process (not just typed and assumed, per this project's own recurring ADR-047 lesson), all four required apps (Updater/Auditor/Seedvault/PdfViewerGOS) confirmed present in a fresh installed-files*.txt, 43m32s, 1714 steps.

Signed with the alpha key (265ade399a0f3ee65003e56daef26a8f4d70e6a4), matching ADR-062/064's exact parameters (SHA256_RSA4096, rollback index 1783209600, --padding_size 65536), 13/13 independently verified on two machines (the build host and the controller's own workstation, two distinct avbtool 1.4.0 installs).

On the owner's explicit choice, this candidate is AVB-only signed, not whole-package release-signed — its otacerts.zip carries the AOSP test cert, matching ADR-062/064's own precedent for physical duress-unlock validation candidates (which are hand-flashed via fastboot, not delivered via OTA), not ADR-049/050's fixed state; the owner was shown this explicitly before choosing, given the alternative (redoing whole-package release-signing) is a materially bigger, riskier step that has bitten this project before (docs/devices/lynx-ota-server-flash-rollback-corruption-incident.md).

The owner flashed the candidate personally (never by an agent, per this project's standing rule) and dynamic validation followed via adb: the QS footer's "Select user" dialog — the exact ADR-066 leak — and Settings ▸ Users both directly confirmed fixed on physical hardware, screenshot and full UI-text-dump evidence, zero trace of "Owner" anywhere.

The factory-reset "erase all data" screen appears unreachable for the decoy at all (only "Reset app preferences" is offered), consistent with, not contradicting, item 16's admin-gate finding.

3Consequences

Six items (Wi-Fi shared badge/dialog, uninstall dialogs, the status-bar icon, the Multiuser widget, Guardian's cross-user AppOps check, and the new 0007 fix) remain honestly UNCHECKED — no valid trigger fixture existed for any of them (no shared Wi-Fi network, no multi-install app, no DO/PO app) and none were forced into a pass; all six share the same getUsersForUiDisplay primitive already proven correct at the two most severity-critical sites.

4Review when

Revisit the six UNCHECKED items only if a real fixture (a shared Wi-Fi network, a genuinely multi-install app, a real device/profile-owner app) becomes available during some other, unrelated task — do not construct one solely to close this list.

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