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.
Failed second mktemp leaks the selection handshake temp file: cleanup trap installed only after both files exist
Low-severity issue, currently open.
Description
The issue as recorded.
prepare_handshake_files creates selection_file (line 72) then done_file (line 73) but installs the EXIT cleanup trap only at line 75. If the second mktemp fails, set -e exits before the trap exists. The first temp file - the private selection file - stays behind in TMPDIR.
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-k02d-c08.sh
Reproduction steps
Technical steps for your engineers to confirm the issue by hand.
./pocs/crs-260930-k02d-c08.sh
What protects you, and the fix
What limits your exposure today, and the planned remediation.
What protects you now
The leak is one temp file per failed second mktemp (disk full or /tmp mode change); a reboot clears /tmp
The fix
Install the EXIT trap before the first mktemp, wiring the variables as the code assigns them (trap 'rm -f "${selection_file:-}" "${done_file:-}"' EXIT)
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 1 requirements · 1 code files · 1 tests.
- omarchy-menu-select
- menu-dmenu-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-menu-select-handshake-tmp-leak.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.