From: Russell Coker <russell@coker.com.au>
To: selinux@tycho.nsa.gov
Cc: Ian Pilcher <arequipeno@gmail.com>,
Systemd <systemd-devel@lists.freedesktop.org>
Subject: Re: SELinux type transition rule not working
Date: Thu, 2 Mar 2017 13:16:39 +1100 [thread overview]
Message-ID: <201703021316.39263.russell@coker.com.au> (raw)
In-Reply-To: <51816900-3b52-8eb6-bf86-75aa8540fca3@gmail.com>
On Thu, 2 Mar 2017 08:40:49 AM Ian Pilcher wrote:
> I am using systemd's RuntimeDirectory to create a directory for a
> service.
>
> RuntimeDirectory=squoxy
>
> This causes systemd to create /run/squoxy before starting my service,
> but I haven't been able to get the SELinux context set correctly on the
> directory.
>
> I've set file context rules for both /run/squoxy and /var/run/squoxy:
>
> ^/var/run/squoxy(/.*)? all files system_u:object_r:squoxy_var_run_t:s0
> ^/run/squoxy(/.*)? all files system_u:object_r:squoxy_var_run_t:s0
>
> And, indeed, restorecon will set the context of the directory to
> squoxy_var_run_t.
If restorecon gives the correct context and systemd-tmpfiles does too
(according to one of your later messages) then this is a bug in systemd.
It's probably best to raise it in the systemd bug tracker.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
prev parent reply other threads:[~2017-03-02 2:16 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
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 [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=201703021316.39263.russell@coker.com.au \
--to=russell@coker.com.au \
--cc=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.