From: Daniel J Walsh <dwalsh@redhat.com>
To: Stephen Smalley <sds@tycho.nsa.gov>,
Joshua Brindle <jbrindle@tresys.com>,
Karl MacMillan <kmacmill@redhat.com>,
SE Linux <selinux@tycho.nsa.gov>
Subject: File Context problem
Date: Mon, 06 Aug 2007 10:11:21 -0400 [thread overview]
Message-ID: <46B72C09.2040600@redhat.com> (raw)
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=251001
As this bugzilla points out, we are somewhat inconsistant on the handling of file context. Currently we treat homedirs differently then we do file_context generated by a policy module. So the sort order seems to go
semanage fcontext -a : Highest
genhomedircon : Second
semodule -i : third
So the question is should the context of genhomedircon and semodule -i be treated the same.
/etc/selinux/TYPE/context/files/file_contexts
/etc/selinux/TYPE/context/files/file_contexts.homedirs
I think local should override everything else.
--
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 reply other threads:[~2007-08-06 14:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 14:11 Daniel J Walsh [this message]
2007-08-06 14:41 ` File Context problem 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=46B72C09.2040600@redhat.com \
--to=dwalsh@redhat.com \
--cc=jbrindle@tresys.com \
--cc=kmacmill@redhat.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.