|
|
|
|
|
|
|
![]() |
#1 |
i fucking told i type to fucking fast wtf
|
You have a pm
![]()
__________________
<a href="http://www.greenguysboard.com/onthebench/">Join Me For On The Bench </a> |
![]() |
![]() |
![]() |
#2 |
A woman is like beer. They look good, they smell good, and you'd step over your own mother just to get one!
|
suexec cant run on 777 you need to run on 755, its a known issue with all scripts.
|
![]() |
![]() |
![]() |
#3 | |
The only guys who wear Hawaiian shirts are gay guys and big fat party animals
|
It's always nice to avoid having any directories chmod 777, but sometimes necesary.
On the other hand, there is never any reason at all to EVER use SuExec on a dedicated server. Doing so only creates huge security problems. Whoever gave you that advice should either be fired for complete incompetence or enrolled in a system administration class today. The only thing SuExec can do that is good is to protect you against other webmasters on a shared server. It does so at the cost of making you much more vulnerable to outside attackers. What SuExec does is give any visitor to your site complete permissions to change or delete any of your files or directories. On a dedicated server it's exactly the same thing as chmod()ing everything 777. Quote:
Any permissions changes would ned to be done by root, but if they are already owned by "nobody" it may not actually be those files that need to be chmod. IT may be one of the directroies they are in. The directories containing them should be chmod 755, or in rare cases 777. If a directory is 666 or 644 or something you can't access files in it. |
|
![]() |
![]() |
![]() |
#4 | |
Solipsists of the world unite
Join Date: Oct 2003
Location: xxx axis
Posts: 639
|
Quote:
I'm addressing this issue with my hosts now. I'll let you know what they say ![]() |
|
![]() |
![]() |
![]() |
|
|