Methods to Increase Security on suPHP - Restricting who can use php.ini files

[Astral God]

This is what i've done, but the value(s) becomes global values, applied to ALL clients and folders, not only to the one(s) specified... :\

EDIT: Can't understand why, but it's working now...thanks...

 

[cPanelTristan]

Re: Methods to Increase Security on suPHP - Restricting who can use php.ini

The only way I could have seen it not working is if you were using PHP 5.2 rather than PHP 5.3 or higher. PHP 5.2 doesn't recognize the PATH values and makes them global.

 

[mcongosto]

Re: Methods to Increase Security on suPHP - Restricting who can use php.ini

Under this method, even PHP_INI_SYSTEM directives are changeable for that account.

That means that I should be able to disable for example Zend Loader for a particular path, but I'm not able to!

this is what I'm doing:

[PATH=/home/coffee/public_html]
zend_loader.enable = 0

doesn't work since it keeps loading Zend loader, breaking one of my scripts (jreviews) after upgrading to php 5.3

any idea?

thanks!

 

[kokonas]

Re: Methods to Increase Security on suPHP - Restricting who can use php.ini

I want to disable_function (exec, shell_exec, system) for all server accounts and enable them to one account only. Any idea? I am using apchec2.2 & suphp & php5.3

 

[Indianets]

Does PHP 5.3+ method one with user ini works any more?

PHP 5.3.27
Apache/2.2.25

PHP5 handler = suPHP

 

[ANKUR KUMAR]

The above method applies even if someone is using cloudlinux with CageFs and securelink ??