*** This bug is a duplicate of bug 192651 ***
https://bugs.launchpad.net/bugs/192651
** Changed in: sudo (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/5079
*** This bug is a duplicate of bug 192651 ***
https://bugs.launchpad.net/bugs/192651
** This bug has been marked a duplicate of bug 192651
hardy sudo path is always reset
--
sudo built with --with-secure-path is problematic
https://bugs.launchpad.net/bugs/50797
You received this bug notif
I worked around it like this:
mv /usr/bin/sudo /usr/bin/sudo.orig
then create a file /usr/bin/sudo containing the following:
#!/bin/bash
/usr/bin/sudo.orig env PATH=$PATH "$@"
then your regular sudo works just like the non secure-path sudo
--
sudo built with --with-secure-path is problematic
This is really annoying. It might be wise to keep current behavior by
default for security reasons, but there should be a way of overriding it
other than recompiling from source code! Many people ARE in need of PATH
inheritance. I wonder why no maintainers look into it, which seems easy
to come up
I just came across this issue in Feisty, apparently its still there.
A workaround I'm using is to place a link in this secure path to the
command I want to run where it already exists on the filesystem.
--
sudo built with --with-secure-path is problematic
https://bugs.launchpad.net/bugs/50797
Yo
Yes. There *needs* to be a way to override this "feature" without
having to recompile. Nothing worse then security bigots telling you
what's best for your environment and then not giving you a way to turn
it off.
Worse, this only appeared to me with a recent apt-get update of dapper.
It appears
This situation is still the same in Edgy. The current sudo breaks many,
many build scripts by not inheriting the path. There really should be a
way to override this "feature" without having to rebuild the package.
--
sudo built with --with-secure-path is problematic
https://launchpad.net/bugs/507
Rather than dropping --with-secure-path, we should restore sudo's
original ability to override the compiled-in secure path with an entry
in /etc/sudoers. That way there would be no problem with upgrading, as
existing /etc/sudoers would work the same as always. I did some work on
this a month or so
Workaround:
sudo env PATH=$PATH
I am very hesitant to drop --with-secure-path. We cannot
automatically transition existing /etc/sudoers file and we must not
change semantics on upgrades.
** Changed in: sudo (Ubuntu)
Importance: Untriaged => Wishlist
--
sudo built with --with-secure-pa
Looking at it a bit more, the impossibility of overriding --with-secure-
path is an ancient bug: see http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=85123 .
--
sudo built with --with-secure-path is problematic
https://launchpad.net/bugs/50797
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
Worse still, as far as I can tell, it is impossible to respecify
secure_path in the sudoers file. So if, for example, you want to offer
your users easy access to something under /opt, you must recompile sudo.
The hard coding of secure_path also breaks the general Ubuntu convention
(as I understood
11 matches
Mail list logo
