If it is my umask that is at fault, why are the two .cdb files being generated with two different sets of permissions? The only difference between the two whitelist files is that one is being appended to automatically and the other is not. When the .cdb file is regenerated for the whitelist file that I manually update, the permissions are fine.

Andrew

Jason R. Mastaler wrote:
Andrew <[EMAIL PROTECTED]> writes:

I have an auto-append whitelist set up and every time it is updated
and a new .cdb file generated, the .cdb file is given group and
world read/write permission. This just doesn't seem right to me.

This isn't hardcoded anywhere in TMDA, your umask value is what is
determining those permissions.

Try adding the following to the top of your ~/.tmda/config file:

os.umask(077)

This will set the umask, affecting the file permissions of all files
TMDA writes, including the CDB file.


_____________________________________________
tmda-users mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-users

Reply via email to