|
Bugzilla – Full Text Bug Listing |
| Summary: | commands with relative path no longer working | ||
|---|---|---|---|
| Product: | Sudo | Reporter: | mathews.dennis |
| Component: | Sudo | Assignee: | Todd C. Miller <Todd.Miller> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | low | ||
| Version: | 1.9.14 | ||
| Hardware: | IBM | ||
| OS: | AIX | ||
| Attachments: | sudo -V output | ||
Yes, that is a bug that was introduced in sudo 1.9.14. I just committed the fix in https://www.sudo.ws/repos/sudo/rev/e7545a3736c6 This is fixed in sudo 1.9.15p3. |
Created attachment 576 [details] sudo -V output Previously (at least on 1.9.5p2), a config like: user ALL=(root) NOPASSWD: /app/abc/scripts/* Would allow the use of relative names in the command specification. Eg. 'sudo /app/abc/plugins/../scripts/command' But now on 1.9.14p3, only absolute command path is allowed. Eg. 'sudo /app/abc/scripts/command'. I couldn't figure out if this was an intentional change to how sudo works from the changelog and if so when this was introduced