|
Bugzilla – Full Text Bug Listing |
| Summary: | sudo -v does not honor NOPASSWD anymore | ||
|---|---|---|---|
| Product: | Sudo | Reporter: | spidermario |
| Component: | Sudo | Assignee: | Todd C. Miller <Todd.Miller> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | oleksandr |
| Priority: | low | ||
| Version: | 1.8.28 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Attachments: | Fix for bug #901 | ||
|
Description
spidermario
2019-10-15 02:03:02 MDT
Confirming this behaviour on Arch Linux after 1.8.28 upgrade.
As a possible temporary workaround, setting "Defaults verifypw=any" option brings back things to normal.
I have the same question though whether the change was intended. The man page says:
===
By default, if the NOPASSWD tag is applied to any of a user's entries for the current host, the user will be able to run “sudo -l”
without a password. Additionally, a user may only run “sudo -v” without a password if all of the user's entries for the current host
have the NOPASSWD tag. This behavior may be overridden via the verifypw and listpw options.
===
Since there's only one user entry in my configuration, I'd say it contradicts to what the man page says, and thus the behaviour change is erroneous.
Created attachment 529 [details] Fix for bug #901 Now committed as https://www.sudo.ws/repos/sudo/rev/aac35bcd8584 Fixed in 1.8.28p1, out now. |