All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Brindle <jbrindle@tresys.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: "Christopher J. PeBenito" <cpebenito@tresys.com>,
	Karl MacMillan <kmacmillan@mentalrootkit.com>,
	SELinux Mail List <selinux@tycho.nsa.gov>
Subject: Re: [PATCH 3/3] Separate local file contexts into	file_contexts.local
Date: Sat, 12 Aug 2006 09:21:02 -0400	[thread overview]
Message-ID: <44DDD5BE.6020402@tresys.com> (raw)
In-Reply-To: <1155329531.30078.121.camel@moss-spartans.epoch.ncsc.mil>

Stephen Smalley wrote:
> On Fri, 2006-08-11 at 09:34 -0400, Christopher J. PeBenito wrote:
>> Semanage was looking at the main file contexts in some cases, since the
>> local file contexts were merged into the main file contexts.  This patch
>> fixes the code to look at the appropriate file context databases.
> 
> Thanks, merged, although I did make the libsemanage copy file error
> non-fatal (another patch has made several others non-fatal too).
> 

I never saw the other patch, did it not get sent to the list? I have 
some concerns about making those non-fatal, as I already told Karl. 
Leaving labeling files in an inconsistent state on policy update is an 
easy to way to break your system and with no automated reconciliation 
(eg., install the new policy, let it fix the permissions problems then 
reinstall it again automatically to make the labeling files consistent) 
I have serious doubts that the consistency will get fixed. Bailing on a 
policy update is probably better than killing the users network 
connection (for example) where they won't even be able to use the 
internet to find the solution.

Not to mention, anything being installed after the policy (in an rpm 
transaction) will be using the wrong file_contexts file for some amount 
of time before a user even could intervene and reinstall the policy to 
update the context files.

If these issues are fine with others (Karl indicated they were better 
than the alternative in his opinion) thats fine but I want them noted.

I honestly believe they'll create more problems than they will solve. It 
wasn't arbitrary that we made all those errors fatal, we had a system in 
place to be able to back out of a policy install when something that 
would leave the system in an inconsistent state happened.

> Also, I'm not sure that semanage handles conflicts very well presently,
> e.g.
> 	semanage fcontext -a -t login_exec_t '/bin/bash'
> 

we'll check on that.

--
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.

  reply	other threads:[~2006-08-12 13:21 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 [this message]
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

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=44DDD5BE.6020402@tresys.com \
    --to=jbrindle@tresys.com \
    --cc=cpebenito@tresys.com \
    --cc=kmacmillan@mentalrootkit.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.