From: dE <de.techno@gmail.com>
To: selinux@tycho.nsa.gov
Subject: Re: How does matchpathcon/setfiles work?
Date: Mon, 02 Jun 2014 15:27:53 +0530 [thread overview]
Message-ID: <538C4AA1.3030106@gmail.com> (raw)
In-Reply-To: <CAPzO=NycsK+-5EDgtJh8nFx7WjFT0isYyxgrKxqqtrq3SdRgkg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1118 bytes --]
On 06/02/14 12:12, Sven Vermeulen wrote:
>
> Policies do contain paths. They contain path expressions to be more
> precise.
>
> During policy load, the path expressions together with the target
> contexts are extracted and placed in
> /etc/selinux/mcs/contexts/files/file_contexts, which is where tools
> like matchpathcon get their information from.
>
> Wkr,
> Sven Vermeulen
>
> On Jun 1, 2014 5:48 PM, "dE" <de.techno@gmail.com
> <mailto:de.techno@gmail.com>> wrote:
>
> As we know, policies don't contain paths. So the working of
> matchpathcon/setfiles must be based on common sense.
>
> It looks like it knows certain special folders and it's
> appropriate security context, for e.g. home folder contents should
> have files with user_home_t and suggests the correct SELinux user
> for the files/directories based on which user's home folder is it.
>
> Other directories/files should have the same security context as
> the parent directory, like with /opt.
>
> Is this correct?
>
Do the paths have any other purpose other than defining the default
security context?
[-- Attachment #2: Type: text/html, Size: 1928 bytes --]
next prev parent reply other threads:[~2014-06-02 10:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-01 15:19 How does matchpathcon/setfiles work? dE
2014-06-02 6:42 ` Sven Vermeulen
2014-06-02 9:57 ` dE [this message]
2014-06-02 13:20 ` Stephen Smalley
2014-06-02 18:25 ` dE
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=538C4AA1.3030106@gmail.com \
--to=de.techno@gmail.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.