From: Ian Pilcher <arequipeno@gmail.com>
To: Systemd <systemd-devel@lists.freedesktop.org>,
selinux <selinux@tycho.nsa.gov>
Subject: Re: SELinux type transition rule not working
Date: Wed, 1 Mar 2017 17:51:01 -0600 [thread overview]
Message-ID: <fa679ade-ce06-405b-5474-31dfa5b3b394@gmail.com> (raw)
In-Reply-To: <4ed435ac-9344-02a5-23be-4312500e2085@gmail.com>
On 03/01/2017 05:28 PM, Ian Pilcher wrote:
> Per Lennart's response, systemd *should* be honoring the file context
> rules when creating the directory. It's almost as if the directory is
> being created with the proper context, but something is changing it
> after the fact. I have absolutely no idea what that might be, though.
Hmm. Just for grins, I created a tmpfiles config file:
d /run/squoxy 0755 nobody nobody - -
This gives me the correct context on the directory:
drwxr-xr-x. nobody nobody system_u:object_r:squoxy_var_run_t:s0 /run/squoxy
--
========================================================================
Ian Pilcher arequipeno@gmail.com
-------- "I grew up before Mark Zuckerberg invented friendship" --------
========================================================================
next prev parent reply other threads:[~2017-03-01 23:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 21:40 SELinux type transition rule not working Ian Pilcher
2017-03-01 22:25 ` [systemd-devel] " Lennart Poettering
2017-03-02 15:13 ` Simon Sekidde
2017-03-03 15:44 ` Ian Pilcher
2017-03-03 16:01 ` Simon Sekidde
2017-03-03 16:45 ` Simon Sekidde
2017-03-03 19:32 ` Ian Pilcher
2017-03-03 20:19 ` Simon Sekidde
2017-03-03 21:00 ` Ian Pilcher
2017-03-01 22:28 ` cgzones
2017-03-01 23:28 ` Ian Pilcher
2017-03-01 23:51 ` Ian Pilcher [this message]
2017-03-02 6:12 ` Jason Zaman
2017-03-03 15:36 ` Ian Pilcher
2017-03-03 15:47 ` Stephen Smalley
2017-03-02 2:16 ` Russell Coker
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=fa679ade-ce06-405b-5474-31dfa5b3b394@gmail.com \
--to=arequipeno@gmail.com \
--cc=selinux@tycho.nsa.gov \
--cc=systemd-devel@lists.freedesktop.org \
/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.