Permissions since going cgi

[mikethechap]

I'm running xoops. It states that it requires some folders to be have perms set for 777. Particularly, some of the modules say to set the perms to 777. But, my understanding from the update about moving to a cgi configuration is that the perms do not, indeed, should not be set to 777. So far, everything seems to be doing fine with the settings as they were adjusted (755). Some of the modules, though, offer warnings that the permission settings are wrong.

Is that just because of poor coding that assumes that the program is being run with php set up as an apache module? With error messages popping up, I just want to make absolutely sure that 755 will do what needs to be done on those folders that specify 777. The permissions thing always confuses me.

Thanks in advance...

[Gwaihir]

Yeah, that would be incomplete checks from Xoops' end. Apparently they just assume they need 777 and don't look beyond that. I suppose you could file this as a bug over there. It shouldn't be hard for them to improve their checks.

You don't need 777 here and must be VERY carefull when you actually set something to 777 anyway under JagPC's PHP-CGI set-up, because as soon as an executable script (such as a php file) shows up in such a folder with 777 permissions, the webserver shuts stuff down for security reasons.

[mikethechap]

Thanks Wim!

That's kind of what I thought but much more complete than what I knew. I'll make sure all the perms are right this morning. I do appreciate the help.

Mike Davis