Gobuster seems to stop after ~1100 requests? about gobuster HOT 8 CLOSED

This can also be caused because go hast an infinite timeout on requests. If the website sends you to a tarpit, you will wait forever. I implemented a timeout parameter here if you wanna try: #79

from gobuster.

fyi, these cmdlines end with | wc -l
and contain -v
the idea was that I wanted to see how many requests they made before the binary quit working

from gobuster.

Thanks @Viss. I've had a bit of a play with this and I'm seeing inconsistent results. Let me do some more testing and I'll get back to you.

from gobuster.

no worries!
Let me know if there's stuff you want me to try on this side, or if you
want a copy of that dictionary!

On 10/18/16 5:40 PM, OJ Reeves wrote:

Thanks @Viss https://github.com/viss. I've had a bit of a play with
this and I'm seeing inconsistent results. Let me do some more testing
and I'll get back to you.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#35 (comment), or
mute the thread
https://github.com/notifications/unsubscribe-auth/ABrMX9B_aAyMDzsl3htb9WQKawQpnBRVks5q1WcLgaJpZM4KaV7O.

from gobuster.

Nah the dictionaries I have are more than big enough. The one I usually use is 1.5M lines.

I'm seeing different behaviours on local webservers vs remote webservers. Could be that certain attempts are erroring out without being caught.

from gobuster.

I'd like to chime in on this issue—it seems to be happening to me as well. gobuster will randomly stop doing its thing and either hang, or return an evidently cut-down list of results. To be honest, I spent some time trying to track down the issue but I can't seem to pin it anywhere

edit: it seems to have issues with some Cloudflare sites. @OJ is there any timeout/alarm on these connections? I can't seem to find any, it's probably making the threads hang because the net.http client isn't timing out on some non-standard ports (Cloudflare sites often have 2053/2083/2087/2096/8443 open, and gobuster seems to hang on those)

from gobuster.

Hmm I think this has to do with GO channels, I am experiencing the same with gobuster, and recently started to wrote a custom enumeration tool to substitute one I have in bash and notice the same but with portmapping ... also using go channels... related? maybe, or maybe not. https://github.com/ReK2Fernandez/GoEnumerator

from gobuster.

I've never been able to repro this, but I think this is now sorted in 2.0.0. Thanks!

from gobuster.