Incorrect error handling?

[neex]

Incorrect error handling?

[neex]

Hi @geosphere,

What is the expected behaviour in this case?

[geosphere]

The matter is not about termination because of connection error. Pay attention to timing. I am confused about the program running for 12 hours with no visible result. I've checked this several times with similar configuration

[neex]

Agree, that's confusing. Sorry I didn't notice the timing first.

Internally, the exploit tries to modify the environment of the php-fpm workers trough the bug (and by modifying the environment I mean setting PHP_VALUE options from here: https://github.com/neex/phuip-fpizdam/blob/master/attack.go#L10). It may take a long time as each try success with fairly low probability.

Maybe the exploit should exit with failure if no success achieved in some fixed number of tries? Or just print the number of requests made?

[geosphere]

Maybe both options are useful. Print the number of requests - by default. And for automation - fixed tries from command-line key?