From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: Daniel J Walsh <dwalsh@redhat.com>, SE Linux <selinux@tycho.nsa.gov>
Subject: Re: I am attempting to add a secadm_r
Date: Thu, 7 Apr 2005 18:45:44 +0100 [thread overview]
Message-ID: <20050407174544.GY19784@lkcl.net> (raw)
In-Reply-To: <1112893253.27110.62.camel@moss-spartans.epoch.ncsc.mil>
On Thu, Apr 07, 2005 at 01:00:53PM -0400, Stephen Smalley wrote:
> On Thu, 2005-04-07 at 17:46 +0100, Luke Kenneth Casson Leighton wrote:
> > if someone knows of a way to have two logins, one of which requires
> > one password to get to root-with-sysadm_r privileges, and one of which
> > requires a DIFFERENT password to get to root-with-secadm_r privileges,
> > and never the two shall meet, i would be DELIGHTED to hear of such a
> > method.
>
> What prevents you from doing what you describe via two usernames
> in /etc/passwd that both map to uid 0 but have different role
> authorizations in policy/users?
prevents... nothing ... i remember something appearing to go
wrong when i did that last - something to do with samba, it
ended up at the username "root" even though i'd logged in as
"root2".
in this instance, it'd not be a problem.
thanks for prompting me on this, stephen.
> > i have a customer in the process of testing the system i have set up
> > for them and i would like to be able to tell them that it is not
> > necessary to hammer into the operator that they must not do things like
> > disable selinux, edit the policy, i want to be able to tell them the
> > operator CANNOT disable selinux, edit the policy - but they can still
> > run adduser.
>
> CANNOT is too strong for what Dan is suggesting; the operator could
> still likely ultimately gain access to secadm via subversion of anything
> on which secadm relies; the simple role separation suggested by Dan is
> mostly just to reduce likelihood of mistakes by sysadm affecting the
> policy or labeling.
in the scenario i describe, which i mention in case dan could
incorporate it (it may happen to be the same thing), i would like
secadm to be able to do policy / labelling, and for sysadm to _not_
be able to.
if secadm could be drastically restricted to pretty much only be
able to run policy / labelling selinux command tools - even better.
l.
--
This message was distributed to subscribers of the selinux mailing 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:[~2005-04-07 17:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-07 15:38 I am attempting to add a secadm_r Daniel J Walsh
2005-04-07 16:46 ` Luke Kenneth Casson Leighton
2005-04-07 17:00 ` Stephen Smalley
2005-04-07 17:45 ` Luke Kenneth Casson Leighton [this message]
2005-04-07 17:39 ` Stephen Smalley
2005-04-07 18:33 ` Luke Kenneth Casson Leighton
2005-04-19 4:43 ` Russell Coker
2005-04-07 16:54 ` Stephen Smalley
2005-04-07 16:55 ` Stephen Smalley
2005-04-07 17:10 ` Stephen Smalley
2005-04-07 19:25 ` Daniel J Walsh
2005-04-07 19:37 ` Stephen Smalley
2005-04-19 4:32 ` Russell Coker
-- strict thread matches above, loose matches on Subject: below --
2005-04-08 0:50 Chad Hanson
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=20050407174544.GY19784@lkcl.net \
--to=lkcl@lkcl.net \
--cc=dwalsh@redhat.com \
--cc=sds@epoch.ncsc.mil \
--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.