From: Ronan Waide <waider@amazon.com>
To: russell@coker.com.au
Cc: Stephen Smalley <sds@tycho.nsa.gov>, selinux@tycho.nsa.gov
Subject: Re: su and context
Date: Fri, 16 Feb 2007 10:06:33 +0000 [thread overview]
Message-ID: <1171620393.23455.2.camel@waider.desktop.amazon.com> (raw)
In-Reply-To: <200702151843.50749.russell@coker.com.au>
On Thu, 2007-02-15 at 07:43, Russell Coker wrote:
> As a tangent to this, you should be able to just use chown and chmod to make
> rndc usable by non-root. rndc in recent versions of bind just seems to need
> to read the key file - which could be made readable by non-root.
Oh yeah, that's what I've done - to the extent that I've an RPM trigger
that will fix the permissions on the file if I upgrade bind. The default
ISC installation doesn't lock the binary down in this way (and it makes
little sense; the binary's not setuid, and you could simply copy in a
binary from another machine if your target machine were in a non-selinux
environment) so I guess I should take it up with the Fedora packagers.
The key is actually in a different context, too, so you can block access
to it through SELinux.
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-16 10:06 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
2007-02-12 17:59 ` Stephen Smalley
2007-02-15 7:43 ` Russell Coker
2007-02-16 10:06 ` Ronan Waide [this message]
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=1171620393.23455.2.camel@waider.desktop.amazon.com \
--to=waider@amazon.com \
--cc=russell@coker.com.au \
--cc=sds@tycho.nsa.gov \
--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.