php error

[ukfitnes]

Hi,
I have a wordpress site located at http://ukfitness.x10.mx/ which has an plug-in installed called "EWWW Image Optimizer". The plug-in has been working fine up until this morning and it's now showing me the following error.

"EWWW Image Optimizer requires exec(). Your system administrator has disabled this function."

I'm led to believe its something to do with php.. my phpinfo file is here .. http://ukfitness.x10.mx/info.php

Does anyone know how to fix this error..
Thanks

 

[bdistler]

x10hosting's free-hosting disabled PHP Functions --> exec - shell_exec - enable dl - system - passthru - phpinfo

a configuration error - during a free-hosting's server upgrade or maintenance - occasionally allow an unsupported feature - before the configuration error is corrected

 

[ukfitnes]

thanks for the reply but i'm not sure I understand ..
are you saying that when the server was upgraded or updated in maintenance it has now disabled the php function: exec() and will never be enabled
or
will it be corrected in time.

 

[bdistler]

the PHP function [ exec() ] was allowed during the upgrade - but is now disabled again
it will not be allowed (enabled) on x10hosting's free-servers

 

[caftpx10]

Having exec() enabled is a HUGE security threat. Exec() allows server-side shell execution. On a webhost of any kind, that should ALWAYS be disabled as someone can hang the server using SLEEP, reboot the server, shutdown, you name it.
From what I've saw, many things ended up being enabled during the update, php.ini by default disables functions which are to do with process reading and modification, there are many vulnerable functions (to the actual server). X10 is VERY lucky that no one has executed any arbitrary commands which can be fatal during the upgrade.

 

[Dead-i]

Just to clarify - the exec() function was indeed enabled during the upgrade period only. However, this did not pose any major security threats, as any commands run through exec() were "caged", so no actual commands could be run. No commands could be run to damage the server or touch anybody else's files, and nobody should be worried that someone might have manipulated exec() in this way.

The exec() command was disabled afterwards, just in case.

 

[caftpx10]

Just to clarify - the exec() function was indeed enabled during the upgrade period only. However, this did not pose any major security threats, as any commands run through exec() were "caged", so no actual commands could be run. No commands could be run to damage the server or touch anybody else's files, and nobody should be worried that someone might have manipulated exec() in this way.

The exec() command was disabled afterwards, just in case.

Ah right, I had a slight feeling that there was a few things blocked but I didn't think it would be completely protected with it enabled. One step ahead.

 

[ukfitnes]

Thanks everyone for the reply's, it's much appreciated ...