Russell Coker <russell@xxxxxxxxxxxx> 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
