From: Yuri Csapo <ycsapo@mines.edu>
To: linux-admin <linux-admin@vger.kernel.org>
Subject: root access for end users
Date: Fri, 05 Jun 2009 05:34:23 -0600 [thread overview]
Message-ID: <4A2902BF.8030903@mines.edu> (raw)
After a battle of years, "academic freedom" was invoked and very senior
management, in its infinite wisdom, has decided that our users (mostly
researchers) should have root access (or full sudo, which amounts to the
same thing) to their Linux workstations.
Does anybody have experience running a Unix/Linux network like this?
Remember full sudo means the ability to 'sudo su' and become any other
user, making permissions (even across NFS) useless. It also means the
ability to play with/pilfer/replace Kerberos keytabs, allowing one to
impersonate any box to which they have access. The support nightmare
cannot be used as an argument against this because users have convinced
management that "that's what support is for."
All I can do is control the servers and decide how services will be
presented and which hoops users should go through to be able to use
server resources.
The current environment is basically Kerberos authentication, NIS
authorization and NFS/CUPS services. Most of the clients are owned,
built, maintained and supported by my organization, but some users will
use their new found freedom to build/buy their own boxes.
The plan is to move away from NIS to LDAP and from NFS to AFS.
What other problems do people see? Any thoughts and suggestions will be
greatly appreciated.
TIA!
Yuri
next reply other threads:[~2009-06-05 11:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 11:34 Yuri Csapo [this message]
2009-06-06 0:08 ` root access for end users ben
2009-06-06 10:00 ` Glynn Clements
2009-06-08 19:19 ` Yuri Csapo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A2902BF.8030903@mines.edu \
--to=ycsapo@mines.edu \
--cc=linux-admin@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).