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.
add pwfeedback to sudoers file by default for better user experience.
Reported by davidbasilefilho · filed Sep 28, 2025Closed upstream on 2026-02-01. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
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
What do you need?
adding pwfeedback to sudoers file can ensure that the sudo password prompt better aligns with the user's expectation of a password prompt. the user is used to having some kind of feedback in password prompts, and can be confused when first using sudo. and this can help the user identify errors in his password (accidental double clicks, or some other kind of problems). I know I've had these issues over the years.
here is a showcase of how it works:
you can do that by editing the sudoers file with sudo visudo and adding the following line to it:
Defaults pwfeedbackView raw text
### What do you need? adding pwfeedback to sudoers file can ensure that the sudo password prompt better aligns with the user's expectation of a password prompt. the user is used to having some kind of feedback in password prompts, and can be confused when first using sudo. and this can help the user identify errors in his password (accidental double clicks, or some other kind of problems). I know I've had these issues over the years. here is a showcase of how it works: https://youtu.be/_fTYgIGNi5Q you can do that by editing the sudoers file with `sudo visudo` and adding the following line to it: ``` Defaults pwfeedback ```
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.