Skip to main content ↑ ↓
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: No output after using sudo (Read 870 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

No output after using sudo

I am not asked for a password when running commands with sudo. When I press Ctrl+C to cancel the command sudo does ask me for a password, but when I enter it correctly the prompt is cancelled. I've tried running su and it works perfectly fine.
Example:
Code: [Select]
artix:[linux]:~$ sudo pacman -Syy
^C[sudo] password for gov: 

artix:[linux]:~$
Here's my '/etc/sudoers' file in its entirety.
Code: [Select]
## 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/poweroff
#
# Cmnd_Alias    DEBUGGERS = /usr/bin/gdb, /usr/bin/lldb, /usr/bin/strace, \
#                           /usr/bin/truss, /usr/bin/bpftrace, \
#                           /usr/bin/dtrace, /usr/bin/dtruss
#
# Cmnd_Alias    PKGMAN = /usr/bin/apt, /usr/bin/dpkg, /usr/bin/rpm, \
#                        /usr/bin/yum, /usr/bin/dnf,  /usr/bin/zypper, \
#                        /usr/bin/pacman

##
## 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 use a hard-coded PATH instead of the user's to find commands
# Defaults secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
##
## Uncomment to restore the historic behavior where a command is run in
## the user's own terminal.
# Defaults !use_pty
##
## Uncomment to send mail if the user does not enter the correct password.
# Defaults mail_badpass
##
## Uncomment to enable logging of a command's output, except for
## sudoreplay and reboot.  Use sudoreplay to play back logged sessions.
## Sudo will create up to 2,176,782,336 I/O logs before recycling them.
## Set maxseq to a smaller number if you don't have unlimited disk space.
# Defaults log_output
# Defaults!/usr/bin/sudoreplay !log_output
# Defaults!/usr/local/bin/sudoreplay !log_output
# Defaults!REBOOT !log_output
# Defaults maxseq = 1000
##
## Uncomment to disable intercept and log_subcmds for debuggers and
## tracers.  Otherwise, anything that uses ptrace(2) will be unable
## to run under sudo if intercept_type is set to "trace".
# Defaults!DEBUGGERS !intercept, !log_subcmds
##
## Uncomment to disable intercept and log_subcmds for package managers.
## Some package scripts run a huge number of commands, which is made
## slower by these options and also can clutter up the logs.
# Defaults!PKGMAN !intercept, !log_subcmds

##
## Runas alias specification
##

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

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

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

## Uncomment to allow members of group sudo to execute any command
# %sudo ALL=(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) ALL  # WARNING: only use this together with 'Defaults targetpw'

## Read drop-in files from /etc/sudoers.d
@includedir /etc/sudoers.d


Re: No output after using sudo

Reply #1 –
Your sudoers file configures sudo use only by root. Do you have some user-config files in /etc/sudoers.d/ ?

Re: No output after using sudo

Reply #2 –
Quote from: Ambie – on
Your sudoers file configures sudo use only by root. Do you have some user-config files in /etc/sudoers.d/ ?
I have never touched the sudoers file. There does appear to be a file in /etc/sudoers.d/ called '10-installer'. It includes the following:
Code: [Select]
%wheel ALL=(ALL) ALL
Could this be the result of malware? I don't see any reason as to why this should exist in the sudoers file. After deleting it, sudo works but it says my user is not in the sudo file.

Re: No output after using sudo

Reply #3 –
I pasted the output of visudo into /etc/sudoers and it still says that my user is not in the sudoers file. I've never run any funny scripts on this installation so I'm not entirely sure if this issue has been caused by malware.

Re: No output after using sudo

Reply #4 –
Quote from: fart – on
Could this be the result of malware?
Unlikely. This just allows members of group "wheel" to execute commands with sudo.

Are your user in sudoers file? In first post there's not. If not, you need to add it there. Or to add your user to group "wheel" (if your "10-installer" is in /etc/sudoers.d/).

Re: No output after using sudo

Reply #5 –
Quote from: Ambie – on
Quote from: fart – on
Could this be the result of malware?
Unlikely. This just allows members of group "wheel" to execute commands with sudo.
Why did sudo work after deleting it then?
Quote from: Ambie – on
Are your user in sudoers file? In first post there's not. If not, you need to add it there. Or to add your user to group "wheel".
No. I tried running 'usermod -aG sudo' and it says the sudo group doesn't exist. I did the same with the wheel group and it worked but I still get the same output when using sudo.