linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yuri Csapo <ycsapo@mines.edu>
To: linux-admin <linux-admin@vger.kernel.org>
Subject: Re: root access for end users
Date: Mon, 08 Jun 2009 13:19:41 -0600	[thread overview]
Message-ID: <4A2D644D.2020304@mines.edu> (raw)
In-Reply-To: <4A2902BF.8030903@mines.edu>

Thank you everyone for your thoughtful input and suggestions. I thought 
I'd summarize the replies here so everyone could benefit:

Suggested technical solutions: I will be considering them all in the 
near future:

- ACLs
- Limited root kernels: rsbac and lids
- Samba as opposed to NFS
- Don't forget to secure the network infrastructure
- Treat the network as untrusted and mandate VPN

Other kinds of suggestions: some people (correctly I think) have 
identified this as not a technical, but a political problem.

- Hire a lawyer and try to fight it out
- Stand up for your rights
- Try to communicate with users in their own terms

Other comments: I appreciate them all and agree with most :)

- This will be a nightmare
- Don't do it
- Quit
- It's your job. Get over it.


-- 
Yuri Csapo
Academic Computing & Networking
Colorado School of Mines
CT-256
Phone:  (303) 273-3503
Fax:      (303) 273-3475
Email:   ycsapo@mines.edu

Please use the following link to open a service request:
http://helpdesk.mines.edu
===========================================
With a PC, I always felt limited
by the software available.
On Unix, I am limited only by my knowledge.
--Peter J. Schoenster

      parent reply	other threads:[~2009-06-08 19:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-05 11:34 root access for end users Yuri Csapo
2009-06-06  0:08 ` ben
2009-06-06 10:00 ` Glynn Clements
2009-06-08 19:19 ` Yuri Csapo [this message]

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=4A2D644D.2020304@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).