Hi all, and happy holidays! I just updated my several weeks old CVS, and I'm having a permissions problem. When I try to log in, I get the error "Wrong permissions on configuration file, should not be world writable!". I traced this back to an update on 12/8:
* libraries/Config.class.php: Refuse to load config file with world writable permissions, refuse to work with existing config dir.
No matter what permissions I set on my config.inc.php, I get the error, even after I remove basically all permissions. I'm running on Windows 2003/NTFS/PHP 5.1.1/IIS 6. I'm curious if anybody's tested the CVS on this platform yet, since that update. I'm out of ideas how to fix it short of commenting out the source.
- Matt
Hi
On Sun, 1 Jan 2006 18:23:39 -0500 Cyber Dog cyberdog3k@gmail.com wrote:
Hi all, and happy holidays! I just updated my several weeks old CVS, and I'm having a permissions problem. When I try to log in, I get the error "Wrong permissions on configuration file, should not be world writable!". I traced this back to an update on 12/8:
- libraries/Config.class.php: Refuse to load config file with world writable permissions, refuse to work with existing config dir.
No matter what permissions I set on my config.inc.php, I get the error, even after I remove basically all permissions. I'm running on Windows 2003/NTFS/PHP 5.1.1/IIS 6. I'm curious if anybody's tested the CVS on this platform yet, since that update. I'm out of ideas how to fix it short of commenting out the source.
It has been already reported by Sebastian, but I didn't get to fixing till now. As it looks like permissions on Windows doesn't return anything reasonable I just disabled this check for Windows.
Cyber Dog schrieb:
Hi all, and happy holidays! I just updated my several weeks old CVS, and I'm having a permissions problem. When I try to log in, I get the error "Wrong permissions on configuration file, should not be world writable!". I traced this back to an update on 12/8:
- libraries/Config.class.php: Refuse to load config file with world writable permissions, refuse to work with existing config dir.
No matter what permissions I set on my config.inc.php, I get the error, even after I remove basically all permissions. I'm running on Windows 2003/NTFS/PHP 5.1.1/IIS 6. I'm curious if anybody's tested the CVS on this platform yet, since that update. I'm out of ideas how to fix it short of commenting out the source.
just set the file to write-protected! (read-only)
On 1/10/06, Sebastian Mendel lists@sebastianmendel.de wrote:
just set the file to write-protected! (read-only)
-- Sebastian Mendel
www.sebastianmendel.de www.sf.net/projects/phpdatetime | www.sf.net/projects/phptimesheet
I tried setting several sets of restricted permissions, none of which worked. Do you have an exact permission set you know works?
(And I thought Michal said he disabled under Windows, so can it even be tested against the current CVS?)
- Matt
Cyber Dog schrieb:
On 1/10/06, Sebastian Mendel lists@sebastianmendel.de wrote:
just set the file to write-protected! (read-only)
I tried setting several sets of restricted permissions, none of which worked. Do you have an exact permission set you know works?
yes, set file to read-only.
you know ... left click - properties - mark 'read only' under attributes - ok
(And I thought Michal said he disabled under Windows, so can it even be tested against the current CVS?)
i don't know if Michal already implemented this
Hi
On Wed, 11 Jan 2006 09:44:46 +0100 Sebastian Mendel lists@sebastianmendel.de wrote:
Cyber Dog schrieb:
(And I thought Michal said he disabled under Windows, so can it even be tested against the current CVS?)
i don't know if Michal already implemented this
I hope so, but I don't have any windows to verify it ;-)
On 1/11/06, Sebastian Mendel lists@sebastianmendel.de wrote:
Cyber Dog schrieb:
On 1/10/06, Sebastian Mendel lists@sebastianmendel.de wrote:
just set the file to write-protected! (read-only)
I tried setting several sets of restricted permissions, none of which worked. Do you have an exact permission set you know works?
yes, set file to read-only.
you know ... left click - properties - mark 'read only' under attributes
- ok
(And I thought Michal said he disabled under Windows, so can it even be tested against the current CVS?)
i don't know if Michal already implemented this
-- Sebastian Mendel
www.sebastianmendel.de www.sf.net/projects/phpdatetime | www.sf.net/projects/phptimesheet
Sebastian - You're correct, checking read only DOES fix the problem. I was implementing the permissions in the NTFS ACLs (Properties>Security). The NTFS ACL method did NOT seem to work correctly. I'm not familiar with the PHP method for determining file security, but apparently it's not accounting for the NTFS ACLs (either that or I just really screwed up setting them to match...).
Michal - First of all, your fix works fine on Windows, I tested today's CVS. Secondly, when I removed the Windows OS check you added and set read-only as Sebastian suggested, it _did_ work properly. I think if we re-add Windows to the check, the method for setting read only needs to be documented for Windows....even though some may consider it obvious, I'm so used to setting the NTFS ACLs for access rights, I did not even consider setting read only on the entire file.
- Matt
Hi
On Wed, 11 Jan 2006 14:59:29 -0500 Cyber Dog cyberdog3k@gmail.com wrote:
Sebastian - You're correct, checking read only DOES fix the problem. I was implementing the permissions in the NTFS ACLs (Properties>Security). The NTFS ACL method did NOT seem to work correctly. I'm not familiar with the PHP method for determining file security, but apparently it's not accounting for the NTFS ACLs (either that or I just really screwed up setting them to match...).
Michal - First of all, your fix works fine on Windows, I tested today's CVS. Secondly, when I removed the Windows OS check you added and set read-only as Sebastian suggested, it _did_ work properly. I think if we re-add Windows to the check, the method for setting read only needs to be documented for Windows....even though some may consider it obvious, I'm so used to setting the NTFS ACLs for access rights, I did not even consider setting read only on the entire file.
As the check won't work correctly for ACLs (I'm pretty sure that also on Linux, but that's not an issue), I'd keep it disabled for Windows, because there are no levels of unix privileges and all permissions (user, group and others) are reported same by PHP...
-
Cyber Dog -
Michal Čihař -
Sebastian Mendel