https://bugzilla.novell.com/show_bug.cgi?id=861539 https://bugzilla.novell.com/show_bug.cgi?id=861539#c0 Summary: suse.cron-sa-update should set umask before running sa-update Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: All OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: suse+build@de-korte.org QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.21 (KHTML, like Gecko) konqueror/4.11.4 Safari/537.21 When running sa-update from the suse.cron-sa-update, SpamAssassin rules will be updated as root with permissions set to the default set in /etc/login.defs. Usually, this will be 022, so Amavis (which runs as user 'vscan') will be able to read them. However, if for privacy reasons the UMASK in /etc/login.defs is set to something more strict (like 027 or 077), the rules will no longer be readable by Amavis. The obvious fix for this is to set umask 022 in the script before running sa-update. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.