[Bug 1442087] Re: don't run as root by default
Well, the user switching can also apply to writing to user specific bayes databases, even if that too can be solved in other ways. Anyway, I'm not in any position to make any decisions here, I just wanted to provide a bit of context while doing initial bug triage. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to spamassassin in Ubuntu. https://bugs.launchpad.net/bugs/1442087 Title: don't run as root by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1442087/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1442087] Re: don't run as root by default
Yes, thanks for the link and thoughts. I'm currently investigating if I can leave all the SA, amavis and clamav code out of my setup by using the blacklist feature of postscreen*. * http://www.postfix.org/postconf.5.html#postscreen_dnsbl_sites -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to spamassassin in Ubuntu. https://bugs.launchpad.net/bugs/1442087 Title: don't run as root by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1442087/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1442087] Re: don't run as root by default
This user switching is for reading per-user configurations only and I think can be mitigated by making the per-user config world readable. Furthermore from the README.spamd.gz you've mentioned If a fault is found in spamd or spamassassin code, any third party linked-libraries or imported perl modules there is the potential for abuse of both the running uid of spamd, and the uid of the username supplied by spamc (and this could be any user). I'm not sure how many LOC but there is quite a slew of extra code with all the plugins that ship with SA. I question if all this code is maintained with the same attention and security awareness as other parts of the mail stack. I know all other parts are not executed as root. Of course statistics wouldn't have hurt ;-). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to spamassassin in Ubuntu. https://bugs.launchpad.net/bugs/1442087 Title: don't run as root by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1442087/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1442087] Re: don't run as root by default
One reason one might want to run spamd as root is that it allows spamc to be called by multiple users, and have spamd change uid accordingly. See /usr/share/doc/spamassassin/README.spamd.gz for further info ** Changed in: spamassassin (Ubuntu) Importance: Undecided = Wishlist ** Changed in: spamassassin (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to spamassassin in Ubuntu. https://bugs.launchpad.net/bugs/1442087 Title: don't run as root by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1442087/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
