It's probably squid's umask. A umask is a set of bitflags that strips away file permissions when a new file is created. All processes on Unix inherit a umask from their parent (but may change their umask to whatever they like).
Squid's default umask is apparently 027, which means that it strips away write access from users within its group, and strips away read/write/execute access from uses outside its group. You can specify a different umask in your squid config.
In reply to Re: Permissions problem with UpsideDownTernet
by tobyink
in thread Permissions problem with UpsideDownTernet
by Cody Fendant
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |