Heres an example: --with-secure-path=/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin without this, you have to specify the full path! (sudo /usr/local/sbin/blah) attached is a modified sudo-1.6.8_p2.ebuild with this in there. Thanks!
Created attachment 44223 [details, diff] patch for sudo-1.6.8_p2.ebuild patch for sudo-1.6.8_p2.ebuild
missing metadata.xml
yep, it was on my todo list :) I'll commit an update later today.
Sorry, I didnt commit an update after all. the problem is, i'm going to get a lot of bugs about this from people who are used to having the PATH carried over. (I've already had a a few complaints from people used to the env being kept since I changed that behaviour). I'm looking at ways to use the path from /etc/profile, which should be sanitised (ie, users can't use it to break out of shell scripts), and convenient. I'll work on it.
what if you added a use flag for including this default path? ("path")
I would very much like it if you created a use flag for including --with-secure-path in the configuration of sudo.
secure_path is enabled in 1.6.8_p8-r2, the mechanism is not perfect, but the benefits outweigh that i think. Please all test it out and file a bug if it doesnt work for you. Any suggestions for impovement welcome.
