sudo built with --with-secure-path is problematic
Bug #50797 reported by
tblumer
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
sudo (Ubuntu) |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
Binary package hint: sudo
For developers who do cross-compiling (for example), sudo needs to inherit the path of the user invoking the sudo command. A better solution is to build without this option and instead alias 'sudo' to 'sudo -i' in user accounts (or /etc/bash.bashrc). At least this method may be easily undone by developers who need to use the sudo path inheritance. OR, provide a command-line option to permit the path inheritance.
Changed in sudo (Ubuntu): | |
status: | New → Confirmed |
To post a comment you must log in.
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 it) that /etc/environment's PATH entry is authoritative for the system.