Proof Portal
Omarchy
ProbeLabsviewing a historical runA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
omarchy-apply-lock shall test fingerprint enrollment by invoking /usr/bin/fprintd-list for the target user.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
omarchy-apply-lock shall test fingerprint enrollment by invoking /usr/bin/fprintd-list for the target user. The helper shall not resolve fprintd-list through PATH.
when fingerprint_enrollment_queried the apply_lock shall always satisfy fprintd_absolute_path_only
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
A PATH-resolved fprintd-list would run attacker-controlled code as root during install or upgrade.
Verification & provenance
How this requirement was checked: the review trail, edit history, and the machine-analysis status terms (each ⓘ explains what it means).
Review
- Status
- in_review
- Reviewer
- Kimi Dogfood · AI agent
- Reviewed
- Sep 12, 2026, 23:50 UTC
History
- Created
- Sep 12, 2026, 19:43 UTC · Kimi Dogfood · AI agent
- Modified
- Sep 12, 2026, 23:32 UTC · Kimi Dogfood · AI agent
Hazard review
- scenarioreviewedaccess_deniederror_handlingboundary
Worst case: a PATH-resolved fprintd-list runs attacker-controlled code as root during install or upgrade. access_denied: invoking /usr/bin/fprintd-list by packaged absolute path refuses any PATH-supplied substitute; the requirement is the refusal. error_handling: a probe failure or nonzero exit is treated as not-enrolled and routes to the removal branch, the fail-safe direction. boundary: the executable-bit check on the absolute path is the present-but-not-executable edge feeding the same removal branch. Catalog 1.11.0 re-review: input_domain not applicable, it invokes fprintd-list by absolute path and reads only its exit status. concurrency_scale not applicable, one probe per apply-lock run.
- propertynot applicable
One probe feeding one branch; no algebraic or repeated-application surface.
- structuralnot applicable
Fixed literal path invocation; no encoding, memory, or format-string surface.
- domainnot applicable
Local exec of a packaged binary under a restricted PATH; name_resolution_pre_chroot evaluated and not applicable: there is no chroot or sandbox entry, and the absolute path leaves nothing to resolution.
Change history
Every recorded revision of this requirement's source file — newest first, each with its commit message and the diff for that change.
Review history
Human and AI-agent approvals of this requirement — the 'why was this approved' lineage, each with the reviewer's justification and the code it cites.
- Kimi Dogfood · AI agentApprovedSpec conformanceSep 12, 2026 · 3 weeks agoREVIEW-10
Enrollment query invokes /usr/bin/fprintd-list by absolute path only; PATH resolution is never used, matching fprintd_absolute_path_only.
Cited code (1)
Open known issues
Findings currently open against this requirement — issues its verification surfaced that are not resolved yet. Each links to the full finding.
Obligations
What this requirement must witness to be considered satisfied — the required evidence, and the tests that discharge each one.
The tests that discharge each obligation aren't available for a historical run
The evidence matrix behind each obligation comes from the live audit index, which can't be rebuilt for a past commit. Nothing here means unknown — not that the requirement has no obligations.
Formula evidence
The formal formula behind this requirement, the variables it is written over, and the tests that exercise it (each term is explained inline).
Formula evidence
The formal formula behind this requirement, the variables it is written over, and the tests that exercise it (each term is explained inline).
FRETish formula
when fingerprint_enrollment_queried the apply_lock shall always satisfy fprintd_absolute_path_only
Witnesses· 3 scenarios total
- apply-lock-test.sh:1exercises 3 condition scenarios
MC/DC truth table· 3 rows
Each row assigns the formula's conditions (T/F) and shows the Result— the formula's value for that input row, not a test pass/fail. A row proves a condition when flipping only that condition flips the outcome. The test that covers each row is linked.
mcdc:ignoreNo-actionfalse-result row satisfied by designUncoveredneeds a covering test| # | fingerprint_enrollment_queried | fprintd_absolute_path_only | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | fingerprint_enrollment_queried | |
| 2 | T | F | F | fingerprint_enrollment_queried | |
| 3 | T | T | T | fprintd_absolute_path_only |
Its place
How this requirement connects — what proves it, what it affects, and what it rests on. Authored links only here; automatically derived links come from the audit index.
Loading graph…
Trace evidence
The concrete artifacts linked to this requirement — implementing code, verifying tests, documents, and the findings raised against it.
Impact
Blast radius — authored trace links only (automatically derived links come from the audit index and aren't shown here).
Impact
Blast radius — authored trace links only (automatically derived links come from the audit index and aren't shown here).
If you change this
Files to re-check (1)
- omarchy-apply-lockbin/omarchy-apply-lock
Tests to re-run (1)
- apply-lock-test.shtest/shell.d/apply-lock-test.sh
What this rests on
Discussions
Discuss this with the proof team. Nothing changes in your audit automatically — you open a request and a staff member records any outcome inside the thread.