All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Pilcher <arequipeno@gmail.com>
To: selinux@tycho.nsa.gov
Cc: Systemd <systemd-devel@lists.freedesktop.org>
Subject: SELinux type transition rule not working
Date: Wed, 1 Mar 2017 15:40:49 -0600	[thread overview]
Message-ID: <51816900-3b52-8eb6-bf86-75aa8540fca3@gmail.com> (raw)

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.

I've also added a type transition rule, attempting to get the correct
context applied automatically when systemd creates the directory:

type_transition init_t var_run_t : dir squoxy_var_run_t "squoxy";

But the directory is still being created as var_run_t:

drwxr-xr-x. nobody nobody system_u:object_r:var_run_t:s0   /run/squoxy

What am I doing wrong?

-- 
========================================================================
Ian Pilcher                                         arequipeno@gmail.com
-------- "I grew up before Mark Zuckerberg invented friendship" --------
========================================================================

             reply	other threads:[~2017-03-01 21:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-01 21:40 Ian Pilcher [this message]
2017-03-01 22:25 ` [systemd-devel] SELinux type transition rule not working 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

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=51816900-3b52-8eb6-bf86-75aa8540fca3@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.