Archived Boards and Threads... > Parham's PHP Tutorials

Why chmod 777 is NOT a security risk

<< < (20/21) > >>

GravuTrad:
for those who understand french and who don't believe that cause thieves exist we have to let our house's door open (without be present)...:

http://www.php-maximus.org/Maximus_CMS_post_t_7357.html

MacGig:
I had things set to 777 once and got hacked, the host said that is why. so Im confused.

can someone list what files should be 777, 775, etc? AFTER the install or upgrade?

IchBin™:
Getting hacked isn't caused by 777. Sounds like you're host doesn't know what they're talking about IMO. Getting hacked is usually through bad code that isn't secure, which allows a hacker to exploit the code to do things on the server. Simply having a file set to 777 isn't an exploit. If that was the case, there would be FAR more sites getting hacked out there...

Skhilled:
Very true. :)

philesq:
I would prefer to use 755 which is working, but would like to use package manager.  I could temporarily change the necessary files to 777, use package manager and then change the files back to 755.  Which files what I need to change to 777?

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version