https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6709

Kevin A. McGrail <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |[email protected]
         Resolution|                            |WONTFIX

--- Comment #1 from Kevin A. McGrail <[email protected]> 2011-11-27 17:21:16 
UTC ---
(In reply to comment #0)
> Using a global umask of 077 and running sa-update results into rules/dirs to 
> be
> u=rwx,g=,o=. I found a old debian bug which seems to be related
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=491232 .
> Not sure if this has ever been forwarded to you guys...
> 
> I think sa-update should use by default a umask of 022 and also provide a
> option to set a custom umask by using e.g. --umask 077.
> 
> I guess in the most cases rules/dirs should have 022.

I would argue this is an OS dependent issue and is a downstream issue. 
sa-update does not currently change the umask as best I can tell.

So if you want a umask of 022, set your os umask to 022 globally or for your
account. 

Or, if needed write a wrapper script to launch sa-update after setting a system
appropriate umask.  

This might be a good thing to document but I don't see it as a bug for
sa-update.

Out of curiosity, what was the workaround in debian?  I couldn't find anything
really pointing to the fix.  I'm guessing it's what I described above as shown
in trunk in debian/spamassassin.cron.daily which sets umask 022 before calling
sa-update.

So a simple script for you that does the same would likely be in order.

-- 
Configure bugmail: 
https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

Reply via email to