From: Tom <tom@lemuria.org>
To: Stephen Smalley <sds@tislabs.com>
Cc: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: split admins
Date: Wed, 24 Apr 2002 16:28:23 +0200 [thread overview]
Message-ID: <20020424162823.B14745@lemuria.org> (raw)
In-Reply-To: <Pine.GSO.4.33.0204240955190.17117-100000@raven>; from sds@tislabs.com on Wed, Apr 24, 2002 at 09:59:37AM -0400
On Wed, Apr 24, 2002 at 09:59:37AM -0400, Stephen Smalley wrote:
> When the example policy was originally being developed, there was an
> initial attempt to provide such a distinction between a system
> administrator and a security administrator, but the separate role was
> discarded because it turns out to be very difficult to truly enforce a
> separation between these two roles without severely limiting the system
> administrator role, making it relatively useless. The topic has also come
> up previously on the list, e.g. see
> http://marc.theaimsgroup.com/?l=selinux&m=100799744813965&w=2.
I'll check that discussion and give it a go. I'm happy with not doing
away root=god. I'm more interested in having, say, an application-level
admin (control over the daemons, network services, whatever). Just
thought a security admin would be a useful thing to start this with.
--
http://web.lemuria.org/pubkey.html
pub 1024D/D88D35A6 2001-11-14 Tom Vogt <tom@lemuria.org>
Key fingerprint = 276B B7BB E4D8 FCCE DB8F F965 310B 811A D88D 35A6
--
You have received this message because you are subscribed to the selinux list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2002-04-24 14:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-24 13:45 split admins Tom
2002-04-24 13:59 ` Stephen Smalley
2002-04-24 14:28 ` Tom [this message]
2002-04-24 14:09 ` Stephen Smalley
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=20020424162823.B14745@lemuria.org \
--to=tom@lemuria.org \
--cc=sds@tislabs.com \
--cc=selinux@tycho.nsa.gov \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.