From 82efcc09270561838217672592dbe6e651aafa88 Mon Sep 17 00:00:00 2001 From: Matthijs Kooijman Date: Mon, 27 Apr 2009 15:55:06 +0200 Subject: [PATCH] spamassassin: Run as user "spamd" instead of root. When running as root, spamd will run as whatever user the client claims to be, to read preferences. Since this is not-so-secure, we'll just run as an unprivileged user to begin with (since we don't do per-user privileges anyway). --- etc/default/spamassassin | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/etc/default/spamassassin b/etc/default/spamassassin index b61c44b..9c16138 100644 --- a/etc/default/spamassassin +++ b/etc/default/spamassassin @@ -14,7 +14,14 @@ ENABLED=1 # make sure --max-children is not set to anything higher than 5, # unless you know what you're doing. -OPTIONS="--create-prefs --max-children 5 --helper-home-dir" +# We run spamd as the user "spamd", which was created specifically for running +# spamd, using: +# adduser --system --home /var/lib/spamd --disabled-login --disabled-password spamd +# By default, spamd runs as root, dropping privileges to whatever username the +# client claims to have, which is not-so-secure IMHO. There shouldn't be any +# any clients other than exim that can access spamd, but since we don't store +# any user preferences, let's just run as an unprivileged user. +OPTIONS="--create-prefs --max-children 5 --username spamd" # Pid file # Where should spamd write its PID to file? If you use the -u or -- 2.30.2