Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhancement Reqeust: Status and Pause/Resume #18

Open
h121h opened this issue May 20, 2016 · 14 comments
Open

Enhancement Reqeust: Status and Pause/Resume #18

h121h opened this issue May 20, 2016 · 14 comments

Comments

@h121h
Copy link

h121h commented May 20, 2016

What is the plausibility of you adding a status hotkey to return where gobuster is currently at in the wordlist and also a pause/resume? Or a switch to start at a specific position in a wordlist?

@OJ
Copy link
Owner

OJ commented May 23, 2016

Hi @h121h,

Thanks for the request. I think the most reasonable thing to do would be to add support for pause/resume, and it wouldn't be too hard to do either. The other things are a little more difficult, because:

  • The mechanism used for concurrency separates the parsing of the wordlist from the workers doing the work.
  • The workers have no visibility of the source of the words (and shouldn't, they should just handle the case for that word).
  • The main thread that parses the list has no visibility of what words have been successfully processed.

There'd have to be a bit of work in synchronising across the two to know what has been parsed and what hasn't. It's not impossible by any stretch, but I would question the value gained vs the effort to add the feature.

As far as "start from word X" is concerned, that would probably not be useful unless you knew where you stopped, so that might be moot at this point.

How about we go ahead with pause/resume, and at the same time add the ability to write directly to file as well as console so that UI interaction doesn't pollute the output? Sound ok?

@OJ OJ self-assigned this May 23, 2016
@h121h
Copy link
Author

h121h commented May 25, 2016

Hi @OJ,

That makes perfect sense and sounds like a plan. Thank you much for the quick response.

@OJ
Copy link
Owner

OJ commented Oct 30, 2017

This is still on the cards, I hope to at least be able to get this going by the end of the year.
NEED MORE TIME!

@firefart
Copy link
Collaborator

status progress is implemented in #79

@BitThr3at
Copy link

Is there any progress in this enchantment of "pause/resume" option ?

@demiscuzz
Copy link

I have often a need to pause ?? any updates?

@OJ
Copy link
Owner

OJ commented Jun 9, 2020 via email

@demiscuzz
Copy link

No way.... How would one go about pausing the a gobuster scan?

@OJ
Copy link
Owner

OJ commented Jun 9, 2020

Hrmm.. I think I might be wrong! I though I had implemented that, but based on the current code, I'm full of shit :P

Sorry, leave it with me.

@elbae
Copy link

elbae commented Jul 27, 2020

Hi, any plan for this feature?

@wifiuk
Copy link

wifiuk commented Dec 24, 2020

This would be handy to have, if it has not already been done

@n0kovo
Copy link

n0kovo commented Mar 15, 2022

BUMP

@hazeyez
Copy link

hazeyez commented Jun 9, 2022

was 7 years enough time? ;P

gobuster needs pause/resume feature

@firefart
Copy link
Collaborator

firefart commented Jun 9, 2022

was 7 years enough time? ;P

gobuster needs pause/resume feature

feel free to open a PR based on the dev branch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants