/etc/cron.daily/spamassassin calls sa-update with potentially incorrect umask
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
spamassassin (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
ubuntu 14.04.1 LTS
Packages:
spamassassin (3.4.0-1ubuntu1)
amavisd-new (1:2.7.1-2ubuntu3)
This report has to do with a problem between the interaction of the spamassassin and amavisd-new packages, but the problem is with /etc/cron.
/etc/cron.
su - debian-spamd -c "sa-update --gpghomedir /var/lib/
Since su is invoked with the "-" option, sa-update executes with the default umask of user debian-spamd. In my case that is 007, causing the updated rules , i.e. /var/lib/
It appears someone attempted to correct this by adding the line:
umask 022
immediately above the call to su mentioned above. This in ineffectual however due to su being called with "-". A fix is to change the above su call to this line:
su - debian-spamd -c "umask 022; sa-update --gpghomedir /var/lib/
A file with the output of 'ubuntu-bug --save=/tmp/sa-bug spamassassin' is attached.
Thank you for taking the time to report this bug and helping to make Ubuntu better.
Is your umask 007 because you changed the system default? I'm asking to understand whether this will affect all spamassassin/ sa-update/ amavisd users by default, or if it only affects others who have changed their system umask.
spamassassin is maintained in Debian, so to make progress on this bug somebody needs to verify if Debian is affected by this problem and if it is then to report a bug in the Debian bug tracking system if there isn't a bug there already.