Date: Wed, 11 May 2005 16:59:07 -0500 From: Trevor Sullivan <pcgeek86@gmail.com> To: David.Bear@asu.edu Cc: freebsd-questions@freebsd.org Subject: Re: best practices for administration Message-ID: <4282802B.1000106@gmail.com> In-Reply-To: <20050511170133.GD10213@asu.edu> References: <20050511170133.GD10213@asu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 David Bear wrote: > Since the BSD community seems to be more security conscious than > other (read windows system administrators) groups, I wanted to see > if anyone here would have any pointers to best practices documents > when administering ANY operating system, not just FreeBSD. I am > assuming that many of you must manage other operating systems as > well. > > The nexus of my query lies in my attempt to have our central IT > folks issue additional identities for users to have when > administering the systems versus doing productivity work on them. > I'd like to understand what is done generally when granting users > permissions to do things on the operating system that imply > 'administration', ie installing software, adding printers, > modifying system scripts, etc. There are some here who think that > putting standard user ID's into administrative 'groups' is > sufficient for granting such priveledges. > > hopefully, I'm not being too obscure. A while ago I happened across the CentOS documentation (copied from RedHat's basically) which you can find here: http://www.centos.org/docs/4/. This has been quite helpful for me, especially regarding things such as user notification, problem resolution etc. - -Trevor -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (MingW32) iD8DBQFCgoAqoGycRpOgdeERAmRpAKDLu9LWcAZHpB2ke3pB0bl2S91AwQCeIrf3 8kMj+UdYHASQPWViTfqQsDk= =A0JV -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4282802B.1000106>