hi all.
with the last commit r3829 you'll be warned (in testing connection
phase) about this kind of things with something like:
[10:18:16] [INFO] testing connection to the target url
[10:18:46] [CRITICAL] connection timed out to the target url or proxy,
sqlmap is going to retry the request
[10:18:46] [WARNING] if the problem persists please try to rerun with
the --random-agent switch turned on
[10:19:17] [CRITICAL] connection timed out to the target url or proxy,
sqlmap is going to retry the request
[10:19:48] [CRITICAL] connection timed out to the target url or proxy,
sqlmap is going to retry the request
kr
On Tue, May 3, 2011 at 10:10 AM, Miroslav Stampar
<mir...@gm...> wrote:
> hi all.
>
> if you are encountering simptoms like this:
>
> [10:01:17] [INFO] testing connection to the target url
> [10:01:47] [CRITICAL] connection timed out to the target url or proxy,
> sqlmap is going to retry the request
> [10:02:18] [CRITICAL] connection timed out to the target url or proxy,
> sqlmap is going to retry the request
> ...
>
> - while you are able to connect to the target url via browser, please
> use --random-agent to get it solved
>
> thing is that probably either sqlmap is blacklisted by some IDSes
> around or the web server itself just refuses requests with "uncommon"
> user agents (to prevent spidering and stuff).
>
> conclusion, use --random-agent in those strange "connection timed out" cases.
>
> kr
>
> --
> Miroslav Stampar
>
> E-mail: miroslav.stampar (at) gmail.com
> PGP Key ID: 0xB5397B1B
>
--
Miroslav Stampar
E-mail: miroslav.stampar (at) gmail.com
PGP Key ID: 0xB5397B1B
|
