PHPsuexec VS suPHP

Any comments

[henry0]

The idea of making yourself totally owner of your scripts is a fine one for it implies that only file owner could exec them.

There are some drawbacks for example register global needs to be off (not that I need it to be on) and safe mode needs to be on or off which is fine but in a shared server environment one cannot set some virtual accounts on and others off
Got to be one or the other but no combo.

Plus using the Zend optimizer might call for a few tweaks in php.ini
<<<
To enable Zend optimizer with PHPSuexec do the following by placing php.ini in your target folder for those who are using it.
register_globals = On
zend_optimizer.optimization_level=15
zend_extension="/usr/local/Zend/lib/ZendOptimizer.so"
>>>
other FAQ:
PHPsuexec seems to be running out of lifes
And I heard a few calls for
SuPHP
Your thoughts? Is it really a good security implementation? is it a must?

[coopster]

I'm not quite sure what you are asking here, henry0? Are you asking what the advantages/disadvantages to using a php wrapper might be?

[henry0]

Well I guess yes

A good question would be:
Is it a must have?
If so is the later one the better?

Thanks

[coopster]

Is it a must have?

No.

If so is the later one the better?

I honestly could not tell you which is better. I just know that after reading the Apache docs on suexec [httpd.apache.org] I couldn't find any reason why I should run programs under user IDs different from the user ID of the calling web-server. Seems more of an issue if you manage a shared hosting server -- and I don't ;-)

suexec is used by the Apache HTTP Server to switch to another user before executing CGI programs. In order to achieve this, it must run as root.

[httpd.apache.org...]

I would guess that the PHP variations of this module are doing the same, and if it isn't setup and configured correctly there can be bigger issues.