Greetings from the great beyond...
Matthew.Hannigan at nl.abnamro.com
Wed Mar 15 08:35:06 EST 2000
Good slides Alek.
Another suggestion I would have for manageability
is to use the %group feature as much as possible.
This means the sudoers file needs less maintenance,
hence less resdistribution necessary. It becomes
then user management issue, best solved with
NIS+ or similar.
For the "passwords in the clear" problem, I'd
suggest ssh. But that's another topic/mailing list.
alek at ast.lmco.com on 14/03/2000 23:45:00
To: bryan_nylander at ibs.uscs.com, sudo-users at courtesan.com
cc: (bcc: Matthew Hannigan/NL/ABNAMRO/NL)
Subject: Re: Greetings from the great beyond...
> From: "Bryan L. Nylander" <bryan_nylander at ibs.uscs.com>
> Subject: Greetings from the great beyond...
> To: sudo Mailing List <sudo-users at courtesan.com>
> Hello all,
> Allow me to introduce myself. My name is Bryan Nylander. I go by the
> Internet Nick Blkwolf.
> The reason for writing you.
> I am looking at using SUDO within our company. I have used sudo for
> several years now but nothing at a industry level. There are some
> answers I have been looking for (unsuccessfully up to this point)
> I am interested if any of you know where I could find some of these
> answers at (if this is not the right place)
> 1> /etc/sudoers distribution over several Unix systems.
> I am looking at providing a way for our SysAdmins to
> manage a centralized /etc/sudoers file. We are
> looking at having 1 common sudoers file that all
> systems will have locally. The problem starts when
> we change the master copy of the sudoers file, how
> do we go about getting that copy across multiple
> system (namely 120 unix boxes)
> Has rdist or NIS been used for this by any other
Rdist works fine for us - see my presentation available at the sudo home
page or at:
http://www.komar.org/ -> Misc. Tech Stuff
More information about the sudo-users