[SOLVED] Sudo is can not find program / Path related issues

Alpha90 · 05-29-2015, 10:48 AM

I am toying around with a LFS system and I am suddenly having trouble with sudo not finding binaries in the standard superuser only binary dirs (/sbin /usr/sbin). I am using sudo version 1.8.10p3. The sudoers file parses correctly and I did not modify except to allow users in the wheel group to be able use sudo to call any command. So I imaging something is wrong with the $PATH variable but I am not sure on what it is.

/dev/random · 05-29-2015, 12:03 PM

What does your sudoers file look like?

jefro · 05-29-2015, 04:21 PM

If you can run any command under sudo I'd think that sudo is working. Sudo ls -l for example.

Should work. http://stackoverflow.com/questions/1...-path-on-linux

Alpha90 · 05-30-2015, 10:15 AM

This is my sudoers

Code:

## sudoers file.
##
## This file MUST be edited with the 'visudo' command as root.
## Failure to use 'visudo' may result in syntax or file permission errors
## that prevent sudo from running.
##
## See the sudoers man page for the details on how to write a sudoers file.
##

##
## Host alias specification
##
## Groups of machines. These may include host names (optionally with wildcards),
## IP addresses, network numbers or netgroups.
# Host_Alias	WEBSERVERS = www1, www2, www3

##
## User alias specification
##
## Groups of users.  These may consist of user names, uids, Unix groups,
## or netgroups.
# User_Alias	ADMINS = millert, dowdy, mikef

##
## Cmnd alias specification
##
## Groups of commands.  Often used to group related commands together.
# Cmnd_Alias	PROCESSES = /usr/bin/nice, /bin/kill, /usr/bin/renice, \
# 			    /usr/bin/pkill, /usr/bin/top
Cmnd_Alias	REBOOT = /sbin/halt, /sbin/reboot, /sbin/shutdown , /usr/sbin/pm-suspend

##
## Defaults specification
##
## You may wish to keep some of the following environment variables
## when running commands via sudo.
##
## Locale settings
# Defaults env_keep += "LANG LANGUAGE LINGUAS LC_* _XKB_CHARSET"
##
## Run X applications through sudo; HOME is used to find the
## .Xauthority file.  Note that other programs use HOME to find   
## configuration files and this may lead to privilege escalation!
# Defaults env_keep += "HOME"
##
## X11 resource path settings
# Defaults env_keep += "XAPPLRESDIR XFILESEARCHPATH XUSERFILESEARCHPATH"
##
## Desktop path settings
# Defaults env_keep += "QTDIR KDEDIR"
##
## Allow sudo-run commands to inherit the callers' ConsoleKit session
# Defaults env_keep += "XDG_SESSION_COOKIE"
##
## Uncomment to enable special input methods.  Care should be taken as
## this may allow users to subvert the command being run via sudo.
# Defaults env_keep += "XMODIFIERS GTK_IM_MODULE QT_IM_MODULE QT_IM_SWITCHER"
##
## Uncomment to enable logging of a command's output, except for
## sudoreplay and reboot.  Use sudoreplay to play back logged sessions.
# Defaults log_output
# Defaults!/usr/bin/sudoreplay !log_output
# Defaults!/usr/local/bin/sudoreplay !log_output
# Defaults!/sbin/reboot !log_output

##
## Runas alias specification
##

##
## User privilege specification
##
root ALL=(ALL) ALL

## Uncomment to allow members of group wheel to execute any command

## Same thing without a password
# %wheel ALL=(ALL) NOPASSWD: ALL

## Uncomment to allow members of group sudo to execute any command
# %sudo	ALL=(ALL) ALL

## Uncomment to allow any user to run sudo if they know the password
## of the user they are running the command as (root by default).
# Defaults targetpw  # Ask for the password of the target user
# ALL ALL=(ALL) ALL  # WARNING: only use this together with 'Defaults targetpw'

## Read drop-in files from /etc/sudoers.d
## (the '#' here does not indicate a comment)
#includedir /etc/sudoers.d

%wheel ALL=(ALL) NOPASSWD: REBOOT

I only added from stock these two lines and uncommented %wheel ALL=(ALL) ALL

Code:

Cmnd_Alias	REBOOT = /sbin/halt, /sbin/reboot, /sbin/shutdown , /usr/sbin/pm-suspend

%wheel ALL=(ALL) NOPASSWD: REBOOT

Quote:

If you can run any command under sudo I'd think that sudo is working. Sudo ls -l for example.

Yes sudo is working by raising the privileges of processes that is directly in my path

Code:

/bin:/usr/bin:/usr/local/bin

However sudo is not seeing roots standard path

Code:

/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin

joe_2000 · 05-30-2015, 10:38 AM

I think this discussion covers it pretty well...

I'd also look at Defaults secure_path which is mentioned in one of the comments.

Alpha90 · 05-30-2015, 12:29 PM

I had seen that discussion page before however it did get me thinking. I checked sudo -V on my remote lfs machine and my current machine with sudo working as I intended it and sure enough I forgot to set the --with-secure-path= flag before I compiled so sudo did not have defaulted a $PATH variable and fell back to my restricted users $PATH