----- Original Message ----- From: "Gre7g Luterman" <[EMAIL PROTECTED]> Sent: Monday, August 18, 2003 8:24 PM
> On Mon, 18 Aug 2003 17:44:25 -0700, Stephen Warren > <[EMAIL PROTECTED]> wrote: > > > I'm noticing that my tmda-cgi session files are getting created with > > permissions rwxr-xr-x. Whilst there doesn't seem to be anything private in > > there, I figure it'd be a good idea if they were rwx------. > > > Is setting the umask something tmda-cgi relies on occuring before it's > > started? Or, should Session.py be modified to os.umask(077) prior to > > saving the session file (and perhaps restore it after?) > > tmda-cgi doesn't mess with umask. You can control this yourself by > putting the appropriate umask command in your config or tmdarc file. I tried doing this, but the session files are created before the import of TMDA/Defaults when the session object is being setup for the first time, rather than reloaded - hence, any os.umask() calls in /etc/tmdarc don't take effect until after the session data is saved the first time around. I guess I could wrap tmda-cgi.cgi with a script that sets the umask, or start apache with a different umask, but I think I'd rather see tmda-cgi set the umask itself when it creates the session files. -- Stephen Warren, Software Engineer, Parama Networks, San Jose, CA [EMAIL PROTECTED] http://www.wwwdotorg.org/ _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
