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?

AreaIn the audited areamenu· Decided by agents · verified

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. So far: in the audited area (menu) — decided by agents · verified; matches no known issue — decided by agents · verified; not a duplicate of another report — decided by agents · verified. The outcome (valid, duplicate, not a bug, …) is not decided yet. See the decision.

Original report

### System details

Omarchy 4

### What's wrong?

During installation Omarchy also creates root password, but when someone wants to update their password in system menu they only see Drive Encryption and User options.
So if someone doesn't know the root password exists they can end up with old password still in power which is a security oversight.

Meaning they'll use new password for sudo, logging in, LUKS, but if they'll log in as root in tty or type `su` in terminal they'll use the old password.

### proposed fix:
- Either have the "User" option in "Update→Password" update both the user and root password simultaneously,
- Or there should be an option to update all three (user, root, luks) at once (or just user, root if it's unencrypted setup).

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

• Fixed bypr/13215· confirmed

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.