Hi there!

I am running into an issue that might be related to this, so I haven't filed a new issue; please tell me if I should.

The issue happens with v3.6 when I use --wordlist-offset and -x like in the command:
gobuster dir -u $url -w 1000-words.txt -r -x pdf,txt --wordlist-offset $X

If $X == 0, the progress shows the number of attempts against 3000 (I assume it comes from the 1000 words in the wordlist, times 3 because each word is tried with two different extensions and with no extension).

I struggled to find how to only try the second half of the wordlist:

If I try $X = 1501, I have an error "offset is greater than the number of lines in the wordlist".
If I try $X = 501, gobuster correctly tries the expected 1500 tests, but displays progress in a weird way:
- the progress is shown against 3000 total attempts (fine);
- the initial value is 500 (where, against 3000, I would have expected 1501);
- the final value, when gobuster stops and exits, is 2000 / 3000 (66.67%), which is a bit odd, although consistent with the 1500 tests.

In the end, the work is done, but in my use case (many VMs with different offsets on very long wordlists), it is very misleading and difficult to know when a given VM starts to overlap the tests already done by another VM that had a greater offset.

My suggestion is to either:

make shown progress only rely on the wordlist's number of words, and somehow indicate that each will result in N actual tests; or
make shown progress fully rely on the actual number of tests including, in case there is a --wordlist-offset and some -x file extensions, a starting value being the actual number of tests that were skipped instead of the number of words that were skipped.

Additionally, I would find it great to be able to ignore the N last words of a wordlist, or maybe replace --wordlist-offset by something like --wordlist-slice <range>, where <range> might be "100-200", "100-" or "-200".

Progress goes over 100% #533

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions