Even libvirt itself will configure passt to write log, PID and socket files to different locations depending on whether the domain is started as root (/var/log/libvirt/...) or as a regular user (/var/log/<PID>/libvirt/...), and user_tmp_t would only cover the latter. Create interfaces for log and PID files, so that callers can specify different file contexts for those, and modify the interface for the UNIX socket file to allow different paths as well. Signed-off-by: Stefano Brivio <sbrivio(a)redhat.com> --- contrib/selinux/passt.if | 26 +++++++++++++++++++++++++- 1 file changed, 25 insertions(+), 1 deletion(-) diff --git a/contrib/selinux/passt.if b/contrib/selinux/passt.if index 893395b..6a6105c 100644 --- a/contrib/selinux/passt.if +++ b/contrib/selinux/passt.if @@ -30,8 +30,32 @@ interface(`passt_socket',` type passt_t; ') - allow $1 user_tmp_t:sock_file write; + allow $1 $2:sock_file write; allow $1 passt_t:unix_stream_socket connectto; + + allow passt_t $2:sock_file { create read write unlink }; +') + +interface(`passt_logfile',` + gen_require(` + type passt_t; + ') + + logging_log_file($1); + allow passt_t $1:dir { search write add_name }; + allow passt_t $1:file { create open read write }; +') + +interface(`passt_pidfile',` + gen_require(` + type passt_t; + ') + + allow $1 $2:file { open read unlink }; + + files_pid_file($2); + allow passt_t $2:dir { search write add_name }; + allow passt_t $2:file { create open write }; ') interface(`passt_kill',` -- 2.39.2