Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA 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.
Factory reset retains the previous owner's password hash
Reported by AksharP5 · filed Sep 5, 2026Closed upstream on 2026-09-16 by the merge of PR #10379 (closed by ErikMelton). GitHub close reason: completed.
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- Not yet mapped to any requirement or component.
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
System details
Omarchy quattro at 36e56f4f, on a normal ISO install whose @factory snapshot contains a root password.
What's wrong?
Reset Computer retains the previous owner's root password hash in @factory/etc/shadow and shadow-. The next owner can mount the retained snapshot with administrator access and recover the hash for offline password cracking.
The cleanup uses passwd --lock root, which prefixes the hash with ! rather than erasing it. Account tools also leave backup files. These are retained files, beyond the reset's documented limitation about recovering deleted disk data.
Reproduced with the production reset functions and real account tools against disposable account files. Btrfs and boot operations were mocked; a full VM reset/reboot was not run.
Both the retained baseline and staged reset root should erase the old hashes and account-file backups while keeping root locked until provisioning sets the new password.
View raw text
### System details Omarchy `quattro` at `36e56f4f`, on a normal ISO install whose `@factory` snapshot contains a root password. ### What's wrong? Reset Computer retains the previous owner's root password hash in `@factory/etc/shadow` and `shadow-`. The next owner can mount the retained snapshot with administrator access and recover the hash for offline password cracking. [The cleanup](https://github.com/omacom/omarchy/blob/36e56f4fb463547dd877849bd3bd951410c442e9/bin/omarchy-system-factory-reset#L304) uses `passwd --lock root`, which prefixes the hash with `!` rather than erasing it. Account tools also leave backup files. These are retained files, beyond the reset's documented limitation about recovering deleted disk data. Reproduced with the production reset functions and real account tools against disposable account files. Btrfs and boot operations were mocked; a full VM reset/reboot was not run. Both the retained baseline and staged reset root should erase the old hashes and account-file backups while keeping root locked until provisioning sets the new password. Fix: https://github.com/omacom/omarchy/pull/10379
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
No decision has been recorded yet.