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.
Fingerprint gate fail-open: substring grep treats not-enrolled or failed fprintd-list probes as enrolled
Medium-severity issue, currently open.
Description
The issue as recorded.
The fingerprint gate (bin/omarchy-apply-lock:47-48) greps fprintd-list output for the substring 'finger' with stderr discarded and no pipefail. Real fprintd empty-enrollment text ('User alice has no fingers enrolled ...') contains 'fingers'. The gate therefore takes the ENROLLED branch and installs pam_fprintd for a user with zero prints. A daemon error banner ('Fingerprints' then non-zero exit) also passes because the pipeline status is grep's. The script then configures fingerprint PAM for an account that can never match a print.
Affected requirements
The requirement(s) this issue violates — click through to the spec.
Severity, explained
Why this is rated the way it is — and the scoring signals behind the rating (each ⓘ explains the term).
- why this rating
- Risk-rated
- risk area
- Correctness
- CVE surface
- None
How it's proven
The reproducer — an actual test that drives the real code and shows the issue happening. Run it yourself, or peek the test and the source it covers.
known_issue_reproducer./pocs/crs-260930-g166-c01-c13.sh
Reproduction steps
Technical steps for your engineers to confirm the issue by hand.
./pocs/crs-260930-g166-c01-c13.sh
What protects you, and the fix
What limits your exposure today, and the planned remediation.
What protects you now
Impact covers only installs where fprintd-list reports no enrollment or fails. Password PAM stays primary and fingerprint is additive, so auth keeps working while misconfigured
The fix
Match the enrollment table (line-anchored 'Fingerprints' header plus per-finger rows) and require fprintd-list exit 0 with pipefail; treat any probe failure as not-enrolled
Blast radius
If you touch this issue, what else may need re-checking — the requirements it affects and the code and tests that hang off them. Historical view: authored trace links only — automatically derived links aren't reconstructible for past runs.
Touch this finding and you re-check 2 requirements · 1 code files · 1 tests.
- omarchy-apply-lock
- apply-lock-test.sh
Per-requirement evidence
For each requirement this finding touches: the implementing code, verifying tests, and proof obligations that discharge it.
Per-requirement evidence
For each requirement this finding touches: the implementing code, verifying tests, and proof obligations that discharge it.
Evidence trail
The raw evidence manifests behind this finding — superseded by the resolved reproducer above, kept here for traceability.
Evidence trail
The raw evidence manifests behind this finding — superseded by the resolved reproducer above, kept here for traceability.
- proof/evidence/ki-apply-lock-fprint-gate-fail-open.yaml
Change history
Every recorded revision of this finding's source file — when it was added, edited, or re-classified, with the diff for each change.
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.