Roundup Tracker - Issues

Message4289

Author ber
Recipients ber, tonimueller
Date 2011-04-15.07:42:11
Message-id <1302853331.96.0.145873673414.issue2550693@psf.upfronthosting.co.za>
In-reply-to
Betreff: [Roundup-devel] umask and hostname default with 
roundup-server?
Datum: Freitag, 15. April 2011
Von: Bernhard Reiter <bernhard@intevation.de>
An: roundup-devel@lists.sourceforge.net
Kopie: roundup-users@lists.sourceforge.net

Does anyone rely on the hostname=None default?
Do people conciously set or use the umask for the user that runs 
roundup-server?

I am asking because the suggested patch in 
http://issues.roundup-tracker.org/issue2550693
does wo things:

a) It changes the hostname default to "localhost", which I believe is 
sensible. But I want to know if I need to add something to the 
upgrading 
documentation. I suspect that people are not relying on this.

b) It sets an explicit os.umask(0077) within roundup_server.py.
This would override the umask set for the process before and thus
could make it even less secure. If we need this umask to get a 
different
default I guess we have to make it configurable.
----
As it stands now, I think I'll split out the umask change and apply 
the hostname rectification.
History
Date User Action Args
2011-04-15 07:42:11bersetmessageid: <1302853331.96.0.145873673414.issue2550693@psf.upfronthosting.co.za>
2011-04-15 07:42:11bersetrecipients: + ber, tonimueller
2011-04-15 07:42:11berlinkissue2550693 messages
2011-04-15 07:42:11bercreate