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
Hi! First of all, congratulations for the great App.
I would like to report a behavior I believe will help many users. In the HTTP_url.PM, the code dictates the app should terminate in case of a ping failure:
if(!$ping){
die "[-] Web server didn't respond !\n";
I was testing a windows box where firewall would not allow ping, and modifying the code allowed me to proceed with the test.
While by design, modifying the message to mention 'ping failure' as the cause would narrow down the issue for users.
Continue with your great projects! :)
The text was updated successfully, but these errors were encountered:
mpwill
changed the title
Ping reply as condition to continue the attack
Ping reply as condition to continue the test
Nov 17, 2016
While your bug report still seems to confuse whatever you experienced with some other network protocol the -C command line switch probably solves your problem.
Hi! First of all, congratulations for the great App.
I would like to report a behavior I believe will help many users. In the HTTP_url.PM, the code dictates the app should terminate in case of a ping failure:
if(!$ping){
die "[-] Web server didn't respond !\n";
I was testing a windows box where firewall would not allow ping, and modifying the code allowed me to proceed with the test.
While by design, modifying the message to mention 'ping failure' as the cause would narrow down the issue for users.
Continue with your great projects! :)
The text was updated successfully, but these errors were encountered: