Is permission 755 really needed to run Quickcache?

[simon]

Hello,

Is it really needed to set the wp-config to 755 chmod or can we set it only to 755 only when we change configuration?

I am asking this cause my wp-config was hacked several time while it was on 777....
and now im on 644 but keeps giving me the error :

permissions: Please check permissions on /wp-config.php. Quick Cache needs write-access to this file. Permissions need to be 755 or higher.

Please advice,
Simon

[ovidiu]

please read up on linux permissions
the dangerous part is the last bit so 755 is way less dangerous than 777.
and all that depends on how you run your apache: as mod_php, suPhp or FastGI with suexec...

[simon]

ovidu,

Thanks for the reply.
Right now i have it set to 444 just to make sure. I was hacked both on 777 and 755.
Also in the source of my pages i still get the quick cache messages that page is cached and next cache will be at ....

this means its working right ?

[ovidiu]

you need to understand what you are doing there. read this: http://www.zzee.com/solutions/linux-permissions.shtml

quick summary: 444 means: read only! so no, the cache cannot be written if it is read only!

the right permission depends on your config as I said: who does your webserver run as? www-data? or as your user/group? Find out!

[simon]

Ovidu,

Yes.. I know 444 on the wp-config is read only...

I thought the 755 OR 777 on the wp config is Only needed so we could configure the Settings of Quick Cache but thats not the case i think...?

My cache dir is still 755 and it writes cached pages to that dir still.

In the source of my pages i see that every hour it writes new a cached page just like when i had wp-config on 755 or 777! :

<!-- This Quick Cache file was built for ( www.mydomain.com/ ) in 0.42681 seconds, on May 8th, 2011 at 6:35 pm UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on May 8th, 2011 at 7:35 pm UTC -->


Thats why i think its still working!

Thanks again.

[ovidiu]

I guess its only needed to activate and deactivate QuickCache, since all it seems ot add is this line for activating quick cache: define('WP_CACHE', true);

[simon]

yes, so its working

[williamblake621]

wow such a decent discussion which help me a lot thanks for decent thread.