Details

Recently, an user reported problems to use the OSCPMwin application. The problem was:

a) The server-side script had a scripting error.
b) The OSCPMWin application was unable to detect and report the problem.

This bug report if about the first item.

The problem was that the function php_uname was disabled by disable_function in the server. The script was not aware of that and tried to call the function, resulting in a error string in the script output. This confused the OSCPMWin application.

The expected behavior is: check for disabled functions, if not so important, just don't use them, if critical, crash the script.