From: Ronan Waide <waider@amazon.com>
To: selinux@tycho.nsa.gov
Subject: Re: su and context
Date: Mon, 12 Feb 2007 17:38:19 +0000 [thread overview]
Message-ID: <1171301899.20328.29.camel@waider.desktop.amazon.com> (raw)
In-Reply-To: <1171299200.5265.34.camel@moss-spartans.epoch.ncsc.mil>
On Mon, 2007-02-12 at 16:53, Stephen Smalley wrote:
> The behavior has actually changed over time; you'll find discussions
> about it in the mailing list archives. The original SELinux kept su
> separate from security context changes. Earlier versions of Fedora (and
> RHEL 4) integrated them (via pam_selinux) in an effort to provide
> greater transparency, but this caused its own set of problems (e.g. use
> of su from init scripts, losing continuity of context across su when you
> want it for roles and levels). More recent versions of Fedora (and RHEL
> 5) split them back out again. One might add an option to su to support
> simultaneous newrole, but you don't want it by default.
On the subject of interaction between "old" and "new" security, I was
briefly stumped in my quest to create a bind role account by the fact
that the rndc binary (on FC6) is not actually executable by anyone other
than root, so granting rndc_exec_t doesn't help unless you also change
the binary's permissions. Is this intentional? I had hoped that SELinux
rather than the filesystem would be taken as authoritative on who gets
access, but I can see reasons why this maybe shouldn't be the case, and
perhaps the 'bug' is with the installed permissions?
Cheers,
Waider.
--
Ronan Waide / TechOps EU Systems Engineer / waider@amazon.com
--
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:[~2007-02-12 17:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-10 16:08 su and context Ted X Toth
2007-02-12 16:39 ` Michael C Thompson
2007-02-12 16:53 ` Stephen Smalley
2007-02-12 17:15 ` Michael C Thompson
2007-02-12 17:38 ` Ronan Waide [this message]
2007-02-12 17:59 ` Stephen Smalley
2007-02-15 7:43 ` Russell Coker
2007-02-16 10:06 ` Ronan Waide
2007-02-13 16:51 ` Ted X Toth
2007-02-13 16:56 ` 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=1171301899.20328.29.camel@waider.desktop.amazon.com \
--to=waider@amazon.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.