chown(/var/dovecot/login/ipc-proxy
Can we remove/change this in the source? So we do not have to add the CAP_CHOWN with containers.
chown(/var/dovecot/login/ipc-proxy)
When run as root this has user dovenull, maybe this can be resolved by using a group dovenull?
bash-5.0# ls -arlt total 4 srw-rw-rw- 1 root root 0 Nov 21 22:27 pop3 srw-rw-rw- 1 root root 0 Nov 21 22:27 login srw------- 1 dovenull root 0 Nov 21 22:27 ipc-proxy srw-rw-rw- 1 root root 0 Nov 21 22:27 imap drwxr-xr-x 1 dovecot dovecot 4096 Nov 21 22:27 .. drwxr-x--- 1 root dovenull 60 Nov 21 22:27 .
Maybe this would work
srw-rw---- 1 root dovenull 0 Nov 21 22:27 ipc-proxy
Thought about creating the socket via some setuid c source temporarily, but now this, grrrr
bash-5.0$ dovecot -F Fatal: Dovecot is already running? Socket already exists: /var/dovecot/login/ipc-proxy
-----Original Message----- To: dovecot Subject: chown(/var/dovecot/login/ipc-proxy
Can we remove/change this in the source? So we do not have to add the CAP_CHOWN with containers.
chown(/var/dovecot/login/ipc-proxy)
When run as root this has user dovenull, maybe this can be resolved by using a group dovenull?
bash-5.0# ls -arlt total 4 srw-rw-rw- 1 root root 0 Nov 21 22:27 pop3 srw-rw-rw- 1 root root 0 Nov 21 22:27 login srw------- 1 dovenull root 0 Nov 21 22:27 ipc-proxy srw-rw-rw- 1 root root 0 Nov 21 22:27 imap drwxr-xr-x 1 dovecot dovecot 4096 Nov 21 22:27 .. drwxr-x--- 1 root dovenull 60 Nov 21 22:27 .
Maybe this would work
srw-rw---- 1 root dovenull 0 Nov 21 22:27 ipc-proxy
participants (1)
-
Marc Roos