When 403 (Forbidden), ghauri asks for user input (y/n) even when I have used --batch argument about ghauri HOT 3 CLOSED

That is intentional behavior because usually it is firewall blocking requests so hammering it won't help either way until the bypass is there within ghauri. So not a bug.

from ghauri.

--batch Never ask for user input, use the default behavior

@r0oth3x49 Well then there should be a default behaviour for that 403 Forbidden, that's "N" coz as you said "hammering it won't help" and you haven't added that default behaviour yet.

Actually it's breaking my automation where I am using 8 axiom instances parallely scanning urls using ghauri...If at somepoint the server responds with 403, then the whole automation will break as ghauri will be expecting an input (y/n) whereas it should have taken the default input as N itself and have stopped further scanning as I have already added --batch argument :/

Well if you don't want to change anything then still you can add a feature to stop scanning when server is unresponsive or got 403 more than 3 time which can be used with --batch like this:

ghauri -r req.txt --level 3 --stop_when_unresponsive --batch

from ghauri.

ping @r0oth3x49

from ghauri.