speed of anonymous MongoDB access scan is very slow about nosqlmap HOT 8 CLOSED

just tried to ping one of the ip address, all packet loss, so I guess lack of latency control may be the reason lead to this.

from nosqlmap.

Right now it uses the pyMongo default timeout of 10 seconds. I've had some hosts take this long to connect up especially over the Internet, but I can make this a configurable option. What do you think?

from nosqlmap.

hmm, I donnt know the average time needed to connect to a host, but it may be better to pile those slow hosts into another queue? and will you consider multi threaded?

from nosqlmap.

Yeah, I could experiment with multithreading. In the interim I was
thinking to add an option to ping the host first and if it's down not even
try the pyMongo client against it. That should speed things up
substantially.

On Mon, Jun 16, 2014 at 10:02 AM, ihacku [email protected] wrote:

hmm, I donnt know the average time needed to connect to a host, but it may
be better to pile those slow hosts into another queue? and will you
consider multi threaded?

—
Reply to this email directly or view it on GitHub
#18 (comment).

from nosqlmap.

Try the changes committed to the 0.4 branch. Added option 3 to set an option to try to ping the host before attempting a connection. This sped things up substantially for me. Let me know how it goes.

from nosqlmap.

Implemented Mongo socket timeouts and ping speed in the 0.4 branch. Should be much, much faster. Let me know. Will implement multithread in 0.5.

from nosqlmap.

speed up indeed, only takes 10 min to catch up 0.3's whole day progress

from nosqlmap.

I have 4 seconds set as the socket timeout, I think that's fair over the
WAN. I will probably make this a configurable option in 0.5.

On Mon, Jun 16, 2014 at 8:43 PM, ihacku [email protected] wrote:

speed up indeed, only takes 10 min to catch up 0.3's whole day progress

—
Reply to this email directly or view it on GitHub
#18 (comment).

from nosqlmap.