I recently added /opt/scripts/sbin and /opt/scripts/bin in PATH using env-update. I tried to run "sudo NAME_OF_SCRIPT_FROM_opt_scripts_sbin" and got "command not found" from sudo. Then I run "sudo env | grep -i path" and found that PATH variable differed from one set by /etc/profile (/etc/profile.env) I checked manpage of sudoers and found an options called "secure_path" which was claimed not to be set by default. I checked ebuild of sudo and found that it's not true. It was set by configure script in compile time. So that option is compiled-in and the documentation should be changed appropriately. Reproducible: Always Steps to Reproduce: I use current stable sudo-1.7.2_p1 in my system.
Working on a patch.
Fixed without revbump, sending patch upstream.
Hello, Diego. Good job, but... Noting that secure_path is set by default is far not enough. It's not a flag. That's a variable with default value set during compile time. Please consider pointing, what default value is, in the man page.
Uhm you should probably ask upstream about that then, since I wouldn't be sure how to document that properly.
(In reply to comment #4) > Uhm you should probably ask upstream about that then, since I wouldn't be sure > how to document that properly. > Ok.
The bug report is here: http://www.sudo.ws/bugs/show_bug.cgi?id=370
