Folder permissions, chmod

ultramega · 2008-06-04 10:12:36

Which are correct chmod values for different TXP folders? Just want to check…

ruud · 2008-06-04 11:10:42

That totally depends on your server setup, but 777 is rarely the answer to that question.

the_ghost · 2008-06-04 11:24:46

ruud – won’t 777 for all folders permisions harm site’s security?

ruud · 2008-06-04 11:29:59

Yes (in most cases), which is why 777 is rarely the correct answer (read: permissions should be as strict as the server setup allows)

AndrijaM · 2010-03-11 15:24:10

Hi, this is an old post but it seems it fits to my needs.

I’m moving my sites to another hosting (leaving MT if you must know, yes they were great but not any more, at least not for me).

Anyway, I took VPS, set everything, it’s all fine, but txp gives me errors in diagnostics that tmp, images and files are not writable.
But, when I chmod-em to 777 all fine!

I underastand that 777 is a security risk, and since I’m on a VPS and I can do whatever is necessarily on the LAMP, there must be a way to chmod this files to something else.

Anybody knows what should I do?

Thanks

Last edited by AndrijaM (2010-03-11 15:25:59)

AndrijaM · 2010-03-11 20:12:40

ok, I’ve found the solution, so here it is, if someone needs it:

Keep the permissions 755 (711, 700) and chown to the same user that runs the Apache. With Debian or Ubuntu, this will be the user “www-data”. The command is:

sudo chown -R www-data /path/to/folder

Last edited by AndrijaM (2010-03-11 20:13:12)

Destry · 2016-01-10 15:51:10

I know this old chestnut will make Ruud’s eyes roll, but I’ve always been confused about folder permissions and why permissions on….

/files
/images
/textpattern/tmp

constantly need to be fixed every time I move a site up to or down from production (at least it seems that way).

I keep hearing/seeing that 777 is not safe, and I have no doubt it’s not, but why is it most often the case that only 777 will work?

This isn’t just with web hosts, but my local setup too. The Txp help tip on the associated diagnostic recommends using 755, but I chmod away in Terminal and it works not. This has got to be a confusing/frustrating situation for people (besides me).

I’m curious about what Adrija is saying above, because I’ve not seen that mentioned before, but I don’t quite get what he’s saying. Is it relevant? Can someone clarify?

RedFox · 2016-01-12 10:51:50

Destry wrote #297327:

This isn’t just with web hosts, but my local setup too. The Txp help tip on the associated diagnostic recommends using 755, but I chmod away in Terminal and it works not. This has got to be a confusing/frustrating situation for people (besides me).

Same here … and I chmod away in Transmit (777 it is) … for years now … :(

Last edited by RedFox (2016-01-12 10:52:39)

ruud · 2016-01-12 17:00:34

If 777 works and 755 does not (for folders), then the folders are owned by a different user than the user of the Apache daemon (or whatever webserver software you use). Two ways to solve that:

chown the directories/files to the webserver daemon user.
change the webserver configuration so PHP scripts for your website are run under your username.

Destry · 2016-01-20 10:18:37

ruud wrote #297355:

change the webserver configuration so PHP scripts for your website are run under your username.

Know a source that explains that a bit more? Where I would go in the haystack and what I would do when I got there…

ruud · 2016-01-20 17:52:23

If you’re using Apache, google for mod_ruid2

kai · 2016-01-20 19:22:51

Destry wrote #297500:

Know a source that explains that a bit more? Where I would go in the haystack and what I would do when I got there…

Maybe this could be interesting: processwire.com/docs/security/file-permissions/

Last edited by kai (2016-01-20 19:47:02)

Textpattern CMS

Textpattern CMS support forum

#1 2008-06-04 10:12:36