From: Russell Coker <russell@coker.com.au>
To: "selinux-refpolicy@vger.kernel.org" <selinux-refpolicy@vger.kernel.org>
Subject: /run types
Date: Sat, 09 Mar 2019 10:18:19 +1100 [thread overview]
Message-ID: <6343390.MUIIc35a3h@xev> (raw)
typealias screen_runtime_t alias screen_var_run_t;
type vmware_host_pid_t alias vmware_var_run_t;
typealias boot_t alias bootloader_run_t;
typealias acpid_var_run_t alias apmd_var_run_t;
type arpwatch_pid_t alias arpwatch_var_run_t;
type lircd_var_run_t alias lircd_sock_t;
type munin_var_run_t alias lrrd_var_run_t;
typealias samba_var_run_t alias { nmbd_var_run_t smbd_var_run_t };
typealias vnstatd_pid_t alias vnstatd_var_run_t;
typealias exim_pid_t alias exim_var_run_t;
typealias irqbalance_pid_t alias irqbalance_var_run_t;
typealias ntpd_pid_t alias ntpd_var_run_t;
type policykit_var_run_t alias polkit_var_run_t;
typealias clamd_var_run_t alias clamd_sock_t;
type getty_runtime_t alias getty_var_run_t;
typealias mount_runtime_t alias mount_var_run_t;
iptables_runtime_t alias iptables_var_run_t;
type mdadm_var_run_t alias mdadm_map_t;
typealias restorecond_run_t alias restorecond_var_run_t;
We have the above aliases in the current git policy. The current type names
include *_pid_t, *_var_run_t, and *_runtime_t.
We have 284 other type definitions that include _run_t, of which 274 are
_var_run_t.
Futher grepping found a few other instances of *_pid_t and *_runtime_t.
By far the most common (and most obviously wrong) is *_var_run_t. When using
systemd (and also non-systemd on systems like Debian) a tmpfs on /run is used
and /var/run is a symlink.
I think we should change this to use a common name. If this idea is generally
accepted I'll submit a patch changing all instances of *_var_run_t, *_pid_t,
and *_runtime_t to *_run_t with aliases for the old names.
What do you think?
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
next reply other threads:[~2019-03-08 23:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 23:18 Russell Coker [this message]
2019-03-12 0:53 ` /run types Chris PeBenito
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=6343390.MUIIc35a3h@xev \
--to=russell@coker.com.au \
--cc=selinux-refpolicy@vger.kernel.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.