ObliviOS Developer portal Project site

Home / Decisions / ADR-179

Amend ADR-174 and ADR-175 after the independent review of Compartments.

Proposed, recorded 18 October 2026.

Decision
ADR-179
Date
2026-10-18
Status
ProposedProposed (landed on the build server and module-built 2026-10-18; in lynx image 2026102101, flashed 2026-10-21; the device rows LNK-013 and LNK-014 are not run).
Part
Compartments
Mentions
ADR-174, ADR-175
Mentioned by
ADR-206

1Decision

Amend ADR-174 and ADR-175 after the independent review of Compartments (compartments-review-2026-10-18.md): (F07) refuse broadcast and multicast datagrams between apps on the loopback path and drop a looped-back multicast datagram for an app without a loopback permission; (F08) round the vibrator calibration for every app uid; (F09) keep a valid frequency profile in the rounded calibration; (F06, F05) let apps read accessibility_enabled and their own entry of the notification listener, accessibility service and input method lists.

2Why and evidence

F07 [measured] on lynx 2026101802: a probe received broadcast datagrams of the other probe and the other received a multicast datagram (LNK-013); F06 and F08 read in the source by the author; F09 reasoning from VibratorInfo.java and the aconfig flag of the review. Rejected: widening the settings allowlist by guessed library keys (no measurement of what stock apps read); a per-app settings switch in Settings (a UI patch, not designed).

3Consequences

An app that listens to its own multicast datagrams on the device no longer receives them unless it holds USE_LOOPBACK_INTERFACE; the ingress rule is a new BPF path whose load on a kernel is untested until an image carries it.

4Review when

The BPF program is rejected by the kernel or networking fails to start on lynx; a stock app loses a function through the ingress rule; a further key that apps need turns up (add it, with a reason).

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