Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have some php scripts that need to move, create and delete files and folders. Unless I CHMOD the folders to 777 the php scripts die with errors about permissions. CHMOD’ing the folders to 777 fixes the problem, but after a lot of reading I’m still confused as to whether it’s OK to do or not.
I’ve read that it can be dangerous on shared hosting, but my question is, is it safe to do on a VPS?
VPS or not it does not really matter. Chmod
777means you are giving anyone (any user, incl. system daemons) all permissions possible (which includes read, write and execute) to given file or directory. if you are the only user on the machine, then it reduces the risk (still, if anyone break in, then he would still be able to mess using hacked daemon’s user id). Additionally, if there’re other user accounts on that VPS, setting777lets them put their content into files with said permission (or launch them). Will they do that – who knows. They might, just because they can due to777. In general, rule of the thumb should be give as much permissions as really needed, and nothing beyond that.