From: Dominick Grift <dac.override@gmail.com>
To: Russell Coker <russell@coker.com.au>
Cc: selinux-refpolicy@vger.kernel.org
Subject: Re: /run/systemd/inaccessible
Date: Thu, 27 Feb 2020 13:20:49 +0100 [thread overview]
Message-ID: <87zhd4b4ri.fsf@gmail.com> (raw)
In-Reply-To: <6385652.IY5x3zMeex@xev> (Russell Coker's message of "Thu, 27 Feb 2020 21:39:29 +1100")
Russell Coker <russell@coker.com.au> writes:
> allow systemd_logind_t init_var_run_t:chr_file write;
>
> audit2allow shows me that the above is attempted on Debian/Unstable. What's
> this inaccessible directory about anyway?
systemd-userruntimedir (245) now also creates it in /run/user/%{USERID}
probably used for InaccessiblePath= directive but I am not sure.
>
> # ls -lZ /run/systemd/inaccessible
> total 0
> b---------. 1 root root system_u:object_r:init_var_run_t:s0 0, 0 Feb 27 13:36
> blk
> c---------. 1 root root system_u:object_r:init_var_run_t:s0 0, 0 Feb 27 13:36
> chr
> d---------. 2 root root system_u:object_r:init_var_run_t:s0 40 Feb 27 13:36
> dir
> p---------. 1 root root system_u:object_r:init_var_run_t:s0 0 Feb 27 13:36
> fifo
> ----------. 1 root root system_u:object_r:init_var_run_t:s0 0 Feb 27 13:36
> reg
> s---------. 1 root root system_u:object_r:init_var_run_t:s0 0 Feb 27 13:36
> sock
--
Key fingerprint = FCD2 3660 5D6B 9D27 7FC6 E0FF DA7E 521F 10F6 4098
https://sks-keyservers.net/pks/lookup?op=get&search=0xDA7E521F10F64098
Dominick Grift
next prev parent reply other threads:[~2020-02-27 12:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 10:39 /run/systemd/inaccessible Russell Coker
2020-02-27 12:20 ` Dominick Grift [this message]
2020-02-27 18:13 ` /run/systemd/inaccessible Topi Miettinen
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=87zhd4b4ri.fsf@gmail.com \
--to=dac.override@gmail.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).