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.
Lock-service fingerprint probe fail-open: substring grep treats zero-enrollment fprintd-list output as configured
Medium-severity issue, currently open.
Description
The issue as recorded.
fingerprintCheckProc's embedded probe (shell/plugins/lock/Service.qml:534) is 'fprintd-list "$USER" 2>/dev/null | grep -qi finger'. fprintd-list's stdout for an empty store is 'User NAME has no fingers enrolled for ... Fingerprint Sensor'; grep -qi finger matches the substring, the probe echoes yes, and fingerprintConfigured = true (line 538). The lock screen then offers fingerprint auth to a zero-enrollment user where every attempt fails. Same substring-oracle class as KI-APPLY-LOCK-FPRINT-GATE-FAIL-OPEN but a disjoint file and code site (executed per lock via refreshFingerprintStatus).
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.
./pocs/crs-260930-ttvk-c02.sh
Reproduction steps
Technical steps for your engineers to confirm the issue by hand.
./pocs/crs-260930-ttvk-c02.sh
What protects you, and the fix
What limits your exposure today, and the planned remediation.
What protects you now
wrong fingerprint attempts still fall through to the password field
The fix
Count enrolled fingers (line-anchored 'Fingerprints' table with >= 1 per-finger row) and require fprintd-list exit 0 before echoing yes
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 6 requirements · 3 code files · 5 tests.
- omarchy-system-lock
- LockView.qml
- Service.qml
- system-lock-test.sh
- lock-fingerprint-indicator-test.sh
- lock-missing-pam-test.sh
- lock-blank-fingerprint-test.sh
- lock-password-overflow-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-lock-fprint-probe-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.