Page 1 of 1

Returning chmods after installation

Posted: Tue Dec 12, 2006 3:47 am
by inetmarketing
Hi,

Installation went without a hitch!

in the install text file it says to put the config to 444. Ok, but what about the
directories that were set at 777.

I set them back to 755, but when I tried to even read the instructions or whatever on my introductory default
template I got an error message-
The following directories must be writable by the web server:
tmp/cache
tmp/templates_c

Please correct by executing:
chmod 777 tmp/cache
chmod 777 tmp/templates_c
or the equivilent for your platform before continuing.
I don't like the idea of leaving directories open to the public. Is there another way around this?

-----------------------------------
Note: Had a hacker get in once on an image directory that was left at 777, and they put a file in there that
allowed them shell access. Real nasty! It was open source too.

Robert

Re: Returning chmods after installation

Posted: Tue Dec 12, 2006 11:14 am
by Dr.CSS
I think if you try 775 it may work have you tried to access your image directory, I can't get into mine...

Re: Returning chmods after installation

Posted: Wed Dec 13, 2006 10:33 pm
by inetmarketing
mark wrote: I think if you try 775 it may work have you tried to access your image directory, I can't get into mine...
So, this CMS also has issues huh?

I'm getting pretty turned off by CMS.

Robert

Re: Returning chmods after installation

Posted: Thu Dec 14, 2006 5:27 am
by Dr.CSS
All mine are set to the 777 and no one can get to them, want to try http://multiintech.com/

This is one of the only CMS that I've looked at that doesn't have a major forum thread just for security...

Re: Returning chmods after installation

Posted: Thu Dec 14, 2006 12:44 pm
by tsw
permissions depend on how the server is configured.

for example running php trough suexec makes it run with that user privileges which means that all new files will be created with that user as owner.

Re: Returning chmods after installation

Posted: Thu Dec 14, 2006 7:28 pm
by Dee
secoif wrote: Did you install via a shell? I had to chmod 775 the entire cms directory to get it working?
CMS (and so apache) needs write access on a couple of directories, there's different ways to accomplish that.
I usually do a

Code: Select all

chown apache config.php &&
chown -R apache modules/ uploads/ tmp/cache tmp/templates_c
so apache (or nobody, depending on which user apache uses) gets owner and don't change any permissions.

Regards,
D