I am guessing that this is a bad idea but I want to ask anyway. PHP
runs as the Apache user which is www. I have added www to the mailman
group and this works. I have since removed it but wanted to see whether
that created too much of a security risk?
Thanks - Dave
On Dec 10, 2005, at 12:38
Dave B wrote:
I am guessing that this is a bad idea but I want to ask anyway. PHP
runs as the Apache user which is www. I have added www to the mailman
group and this works. I have since removed it but wanted to see whether
that created too much of a security risk?
It allows apache to access
Does it use the umask setting? If so, it should be setting permissions
to 644 (umask is 022) instead of the 660 that it sets. Is there a way
to change what it uses as standard permissions?
Thanks - Dave
On Dec 9, 2005, at 11:48 PM, Mark Sapiro wrote:
Dave B wrote:
This works fine except
- Original Message ---
Dave B wrote:
Does it use the umask setting? If so, it should be setting permissions
to 644 (umask is 022) instead of the 660 that it sets.
It uses umask, but it sets it to 007 before creating the new file and
restores it afterword, because it
I am trying to create some php forms that use the shell_exec function
to run some of the Mailman command line commands. i.e. I have a script
that lets an admin user enter an email address and then uses the
find_member script to return all lists that email address is in. To do
this I had to set
On Fri, 2005-12-09 at 12:46 -0600, Dave B wrote:
I am trying to create some php forms that use the shell_exec function
to run some of the Mailman command line commands. i.e. I have a script
that lets an admin user enter an email address and then uses the
find_member script to return all
On Fri, 9 Dec 2005, John Dennis wrote:
2) The php script invokes a wrapper just like the CGI does. This is
preferred for a variety of security reasons. It would not be hard to
create a new wrapper from the existing wrapper src code.
I'm giving serious thought to writing a mailman 'server',
Dave B wrote:
This works fine except that for some reason the permissions will
sometimes revert back to 660 and then the script won't work. Only one
config.pck file has to have 660 permissions for the script not to work.
When I change that particular file back to 664 - the script works
again.
