Réf. : Re: Réf._:_how_to_determine _a_proper_sudo_file_contents

[steve.bernier at desjardins.com]

I think what you need is:

userid hostname=NOPASSWD: ALL

You can replace "hostname" with ALL if the sudoers file is distributed across multiple hosts.

BTW, I DO NOT recommand this kind of authorization, you give "userid" access equivalent to root, ie full access.  But... security vs speed vs ease of use is always a
question...

Steve Bernier
Ingénierie détaillée / GIT
Le Groupe CGI
Tél: (514) 281-2393
Fax: (514) 285-3405
Internet: steve.bernier at cgi.ca
________________________________




"john ctr kelly" <john.ctr.kelly at faa.gov> on 2002-01-24 10:57:47

Pour :    <steve.bernier at desjardins.com>, "John CTR Kelly" <John_CTR_Kelly_at_AWAATO200-OPSNET2 at faa.gov>
cc :  <sudo-users at courtesan.com>
Objet :   Re: Réf._:_how_to_determine_a_proper_sudo_file_contents

Steve,

     Thanks for your suggestion.  Still somewhat confused as to how to set
up the access to allow this user access to everything.
would something like this
Cmnd_Alias      TESTING   = /*

be the best or is there another better way?

    Thanks,

    JK