7

Possible Duplicate:
How to run a specific program as root without a password prompt?

I installed fedora 15. I use sudo visudo to modify sudoers file and add the following line:

USERNAME  ALL=(ALL)       NOPASSWD: ALL

I then logout and login. I try doing any sudo command like sudo gvim &... but I am still getting prompted for password.

How do you get NOPASSWD sudo option to work in Fedora 15?

  • Is my syntax wrong?
  • Is there some Fedora 15 thing that is preventing this to work?

UPDATE:

After seeing answers below talking about "the order of your sudoers file" I decided to copy the full sudoers file in here. I took the liberty of removing most white space lines, all comments lines, and all lines containing the string "Default":

root    ALL=(ALL)   ALL
USERNAME    ALL=NOPASSWD:ALL,/bin/mount,/bin/umount

%wheel  ALL=(ALL)   ALL
  • I am a little frustrated... because this is supposed to be soo simple. – Trevor Boyd Smith Sep 15 '11 at 17:21
  • Could this be of help? http://www.linuxforums.org/forum/miscellaneous/138695-solved-nopasswd-etc-sudoers.html (look at the end for the solution) – nico Sep 15 '11 at 17:34
  • wow nico. i went there. and you are correct. the problem was in the ordering of the statements in the sudoers file! If you had posted a full answer I would have given you the upvote/accepted answer. – Trevor Boyd Smith Sep 15 '11 at 17:42
  • I did not know if that was actually the issue and I never used NOPASSWD before... so I just posted it as a comment. At the end, what's important is that you solved the problem :) – nico Sep 15 '11 at 19:03
  • The problem is not related to sudo but to how does fedora intregrates sudo...which is with PAM. You may have the good config lines in the good order in your sudo config, it will not be sufficient on a fedora host: you will have to tune the PAM config for sudo by editing /etc/pam.d/su and add a line like "auth sufficient pam_admin.so trust use_uid" assuming you configured a NOPASSWD sudo config for group admin. – Christophe Furmaniak Dec 04 '14 at 13:34

1 Answers1

10

Often this is caused by the order of statements in /etc/sudoers, make sure that you have any permissions that may override it before you declare NOPASSWD, or it may be overridden by a later command.

Bear in mind that you should not be using sudo with gvim anyway -- graphical programs should be run with gksu, kdesu, or an alternative, otherwise you risk problems (particularly notable are problems with ~/.ICEauthority and other often-essential files).

Chris Down
  • 125,559
  • 25
  • 270
  • 266