Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

looks like all mail users need to have access to /etc/ceph/ceph.client.mail.keyring #258

Open
f1-outsourcing opened this issue Sep 14, 2019 · 2 comments

Comments

@f1-outsourcing
Copy link

I have noticed that not the dovecot user, but all user accounts need to have access to the ceph.client.mail.keyring. Thus when I was testing with user test, test needed to have read access to the keyring file.
I am not sure this is a desirable situation. I would prefer that the access to this file is limited to eg the dovecot user.

@jrse
Copy link
Contributor

jrse commented Sep 15, 2019

This depends on your dovecot configuration I think. Imap/pop3/lmtp/smtp process opens the ceph connection. So the user configured for this processes needs access to the ceph config and keyfiles.

@jrse
Copy link
Contributor

jrse commented Sep 16, 2019

i checked again. We only tested the plugin with virtual users. Currently we are opening the ceph connection as late as possible to save resources. It may be possible to move the open connection forward e.g. to the plugin init function. With some luck this could allow us to read the ceph certificate and configuration with the dovecot user. But this is untried yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants