This is a tricky one. I understand to put NOPASSWD into the sudoers file to allow no passwords. But I'm trying to revert this and came across a server I have that has no trace of NOPASSWD anywhere. There are no files in
When I run
sudo --list, I do see
(root) NOPASSWD: ALL.
sudo -k still doesn't ask for a password. I cannot paste my exact sudoers file as it's on a separate network than this computer. So I will type everything not in comments:
Defaults env_keep = "COLORS DISPLAY HOSTNAME HISTSIZE KDEDIR LS_COLORS"
Defaults env_keep += "MAIL PS1 PS2 QTDIR USERNAME LANG LC_ADDRESS LC_CTYPE"
Defaults env_keep += "LC_COLLATE LC_IDENTIFICATION LC_MEASUREMENT LC_MESSAGES"
Defaults env_keep += "LC_MONETARY LC_NAME LC_NUMERIC LC_PAPER LC_TELEPHONE"
Defaults env_keep += "LC_TIME LC_ALL LANGUAGE LINGUAS _XKB_CHARSET XAUTHORITY"
Defaults secure_path = /sbin:/bin:/usr/sbin:/usr/bin
root ALL=(ALL) ALL
%wheel All=(ALL) ALL
My guess is that something else is causing this as this isn't happening to more recent servers I have built.
I would guess if you were to use this configuration, you won't have any issues. Would any other program/package cause this, like sssd?
This is tied to IPA but there are no sudo rules tied to this server. My last resort to fix this would be to just rebuild the server, but I'd like to figure out what is causing this, if it's another program or just a bug.