Hello, with imapc settings coming from userdb (individual configuration necessary) there exists a security problem if access to auth-userdb socket is given to normal (shell) users: testuser at host:~$ doveadm user user1 userdb: lpmail uid : 1000 gid : 1111 home : /home/user1 namespace : gmail namespace/gmail/list: yes namespace/gmail/subscriptions: no namespace/gmail/separator: . namespace/gmail/prefix: INBOX.gmail. namespace/gmail/location: imapc:~/Maildir/gmail imapc_host: imap.gmail.com imapc_user: someuser at gmail.com imapc_password: cleartextpassword! imapc_ssl : imaps imapc_ssl_ca_dir: /etc/ssl/certs imapc_port: 993 Lutz
On 14.9.2011, at 14.40, Lutz Pre?ler wrote:> with imapc settings coming from userdb (individual configuration necessary) > there exists a security problem if access to auth-userdb socket is given > to normal (shell) users:So don't give it to them? :) Actually this should be pretty much solved with v2.1 defaults. If the auth-userdb socket is 0666 root:root (default now), it requires that the calling process either has root user/group privileges or its uid matches the one returned by userdb, otherwise it won't return any fields.