You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It may be an good idea to implement some workaround designed to change the php's error_reporting level.
For the moment, it is hardcoded in the payload main encapsulator
(at data/tunnel/encapsulator.php file).
For framework maintenance and plugin development purposes, i think it's interesting to have a way to reconfigure this value dinamically.
How to implement it:
I am still hesitant about the proper way to implement it.
A boolean approach consists in setting default value to something like: E_ERROR | E_PARSE
An the 'verbose' value to something like E_ALL
This way we can make it depend of the $VERBOSITY setting, wich already exists, it is a way that privilegiate a minimalistic framework, without having too much settings.
Another aproach, is to create en new setting called $PHP_ERROR_REPORTING (Boolean() type).
Instead of the boolean approach, we can make a $PHP_ERROR_REPORTING setting of type PhpCode(), or, for an extended customisation, we can have a $PAYLOAD_PREFIX variable, which allows user to add anything he wants as payload prefix.
Also, we can convert the $VERBOSITY variable from Boolean() paragygm to a variable of type int, designed to be set with bitwise operations.
Conclusion:
As you can see, i have no idea for the moment on the proper way to implement this great enhancement, so please, feel free to give your opinion ! :)
The text was updated successfully, but these errors were encountered:
Additional notes:
As some scenarios implies prepending a code to each request (i ve already found a scenario where i had to write to encapsulator.php in order to use phpsploit with a target), this enhancement might imply a larger scope.
The largest scope implies to directly use a MultilineBuffer() as encapsulator, which initially loads the provided script.
I really need feedbacks and proposals about this...
Resolved by implementing a PAYLOAD_PREFIX setting, a MultiLineBuffer wich contains a php code buffer that is executed just before any payload execution.
By default, it sets error_reporting to E_ALL ^ E_NOTICE
Description:
It may be an good idea to implement some workaround designed to change the php's error_reporting level.
For the moment, it is hardcoded in the payload main encapsulator
(at data/tunnel/encapsulator.php file).
For framework maintenance and plugin development purposes, i think it's interesting to have a way to reconfigure this value dinamically.
How to implement it:
I am still hesitant about the proper way to implement it.
A boolean approach consists in setting default value to something like:
E_ERROR | E_PARSE
An the 'verbose' value to something like
E_ALL
This way we can make it depend of the $VERBOSITY setting, wich already exists, it is a way that privilegiate a minimalistic framework, without having too much settings.
Another aproach, is to create en new setting called $PHP_ERROR_REPORTING (Boolean() type).
Instead of the boolean approach, we can make a $PHP_ERROR_REPORTING setting of type PhpCode(), or, for an extended customisation, we can have a $PAYLOAD_PREFIX variable, which allows user to add anything he wants as payload prefix.
Also, we can convert the $VERBOSITY variable from Boolean() paragygm to a variable of type int, designed to be set with bitwise operations.
Conclusion:
As you can see, i have no idea for the moment on the proper way to implement this great enhancement, so please, feel free to give your opinion ! :)
The text was updated successfully, but these errors were encountered: