Quote from: smashingred at Jul 18, 2010, 07:47 PM
It is a poor method of server security and allows people to have insecure apps on a shared server making it actually worse off than it would be otherwise. A host who relies on SafeMode on is likely not up on security in shared environments.
I am no expert but it is a pretty big red flag that your host still uses this for "hardening" servers. If you can’t turn it off at the php.ini level I’d look for a new host entirely.
I think what you are saying is that if safe_mode is on it might indicate that the security issue it is trying to solve hasn’t been addressed properly by the hosting company at the server administration level.
I don’t think having safe_mode on *in itself* makes the environment more insecure, or have I missed something?
I suppose what I need to do is find out what that security issue is that safe_mode on is trying to address and whether my host has dealt with it properly.
At the moment I don’t really understand what the security issue is. I thought it might be to stop developers using system commands exec() etc. as that might allow third parties/hackers to execute shell code via a badly designed script, but I think there must be more to it than that.....
I’ve googled it but not found an explanation I understand yet.... any pointers?
Thanks
Mike