http://bugzilla.spamassassin.org/show_bug.cgi?id=3046
Summary: spamd forces unix domain sockets to spamd user owned,
mode 0666
Product: Spamassassin
Version: 2.63
Platform: Sun
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P3
Component: spamc/spamd
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
The README.spamd (on my debian box) points out all the caveats of
running spamd as root if users can connect to it. However, there's
99% of a reasonable mechanism to solve this problem already in place.
spamd and spamc can use a unix domain socket. If I were to make the
socket owned by a particular user (cyrus is convenient for me) and
mode 600, I could run spamd as root, run spamc with the -u flag as
user cyrus (from postfix, in my setup), and have reasonable security
guarantees.
However, when spamd starts up, it unlinks the existing unix domain
socket, creates a new one as the spamd user, and then chmods it to
666! I think it would be very useful in a future version of spamd to
have new flags to set the socket owner and mode (I propose
--socketowner, --socketgroup, and --socketmode). In fact, I've
appended a patch which implements this.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
