RE: [U2] FW: sudo

2006-01-13 Thread Robert DunnMiller
Did you use the visudo command to put yourself in the sudoers file? If not, the change is not recognized, and you will get the security breach notification. Regards, Robert -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wronkiewicz, Terrie Sent:

Re: [U2] FW: sudo

2006-01-13 Thread Michael Doyle
Two questions: Which platform are you on, and how are you editing the sudoers file? On RHEL, you can't just edit the file, you use the command visudo which will file and compile the sudoers file, so to speak. Mike Doyle Unix Developer / Administrator AMO Recoveries On Fri, 2006-01-13 at 07:14

Re: [U2] FW: sudo

2006-01-13 Thread karlp
I believe the visudo command is for SELinux versions so if SELinux isn't install on the RH box, if that's what it is, then you don't have to worry about it. I've always just edited /etc/sudoers and added the line this way: mylogin name ALL=(ALL) NOPASSWD: ALL You don't have to do it that way,

Re: [U2] FW: sudo

2006-01-13 Thread Jeffrey Butera
On Friday 13 January 2006 10:19, [EMAIL PROTECTED] wrote: I believe the visudo command is for SELinux versions so if SELinux isn't install on the RH box, if that's what it is, then you don't have to worry about it. Not true. visudo has been on every box I've ever used (RedHat, Fedora,

Re: [U2] FW: sudo

2006-01-13 Thread karlp
quote who=Jeffrey Butera On Friday 13 January 2006 10:19, [EMAIL PROTECTED] wrote: I believe the visudo command is for SELinux versions so if SELinux isn't install on the RH box, if that's what it is, then you don't have to worry about it. Not true. visudo has been on every box I've ever

Re: [U2] FW: sudo

2006-01-13 Thread Jeffrey Butera
On Friday 13 January 2006 12:21, [EMAIL PROTECTED] wrote: # This file MUST be edited with the 'visudo' command as root. I've never seen that in the files I've edited. I don't edit it much and have probably just gotten used to looking past most of the # lines. But, learn something new every