From: Karl MacMillan <kmacmillan@mentalrootkit.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Joshua Brindle <jbrindle@tresys.com>,
Daniel J Walsh <dwalsh@redhat.com>,
"Christopher J. PeBenito" <cpebenito@tresys.com>,
SELinux Mail List <selinux@tycho.nsa.gov>
Subject: RE: [PATCH 3/3] Separate local file contextsinto file_contexts.local
Date: Wed, 16 Aug 2006 09:00:57 -0400 [thread overview]
Message-ID: <1155733257.10971.0.camel@localhost.localdomain> (raw)
In-Reply-To: <1155732066.18911.4.camel@moss-spartans.epoch.ncsc.mil>
On Wed, 2006-08-16 at 08:41 -0400, Stephen Smalley wrote:
> On Tue, 2006-08-15 at 19:42 -0400, Joshua Brindle wrote:
> > > From: Stephen Smalley [mailto:sds@tycho.nsa.gov]
> > >
> > > On Mon, 2006-08-14 at 10:38 -0400, Stephen Smalley wrote:
> > > > On Sat, 2006-08-12 at 09:21 -0400, Joshua Brindle wrote:
> > > > > Stephen Smalley wrote:
> > > > > > On Fri, 2006-08-11 at 09:34 -0400, Christopher J.
> > > PeBenito wrote:
> > >
> > > Patch below restores the errors to being fatal, with
> > > exceptions being granted for an ENOENT for
> > > file_contexts.local (optional), seusers (was already
> > > non-fatal and optional), and netfilter_contexts (may not
> > > exist in all policies, e.g. legacy ones and ones that are
> > > using compat_net=1).
> > > Acceptable to all parties?
> > >
> >
> > I'm happy with this but does it fix the permission problem? I thought
> > the motivation behind the patch was to be able to install the policy
> > when the policy didn't allow copying of some files? ENOENT will just
> > check if it doesn't exist won't it?
>
> I decided that it wasn't adequate justification, since:
> a) the same kind of permission problem could occur on the kernel policy
> file too, at which point we have to go permissive to recover,
> b) such a denial would reflect a bug in policy, and there is no general
> way to recover from bugs in policy without going permissive,
> c) all such issues would presumably be caught and resolved in
> development and never hit a production system.
>
> So if everyone is satisfied with the patch, I'll go ahead and commit it.
>
It's fine with me since you and Josh are in agreement about this.
Karl
--
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.
prev parent reply other threads:[~2006-08-16 13:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-11 13:34 [PATCH 3/3] Separate local file contexts into file_contexts.local Christopher J. PeBenito
2006-08-11 20:52 ` Stephen Smalley
2006-08-12 13:21 ` Joshua Brindle
2006-08-14 14:38 ` Stephen Smalley
2006-08-14 19:06 ` Stephen Smalley
2006-08-15 23:42 ` [PATCH 3/3] Separate local file contextsinto file_contexts.local Joshua Brindle
2006-08-16 12:41 ` Stephen Smalley
2006-08-16 13:00 ` Karl MacMillan [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=1155733257.10971.0.camel@localhost.localdomain \
--to=kmacmillan@mentalrootkit.com \
--cc=cpebenito@tresys.com \
--cc=dwalsh@redhat.com \
--cc=jbrindle@tresys.com \
--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.