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

Optional flag to cease scan on first 200 response for CTF items? #20

Closed
codingo opened this issue Sep 25, 2017 · 6 comments
Closed

Optional flag to cease scan on first 200 response for CTF items? #20

codingo opened this issue Sep 25, 2017 · 6 comments

Comments

@codingo
Copy link
Owner

codingo commented Sep 25, 2017

Although in a commercial setting catch-all's are quite likely this doesn't always appear to be the case in CTF items. In these cases you don't need vhostscan's catch-all/likepage filtering and instead would want to know about the first 200 response code found.

Potentially there's some value in a flag that will stop the scan and surface results on the first 200 response code that's hit? It's a minor item since they would find the content with a full scan anyway, but one to consider.

@prabhath6
Copy link
Contributor

If i understand correctly, this should return first likepage which matches the given target host. So typically it would output two results, one being the actual host and the other one will be the file likepage.

@codingo
Copy link
Owner Author

codingo commented Oct 4, 2017

@prabhath6 Yup, that's the one. Are you tackling it?

@prabhath6
Copy link
Contributor

yep, can you assign me this task. So i tried running this in windows there was issue in the some file which
is using both tabs and space i will push a fix for that too.
One last this to confirm if user wish to write the results to file, there should only be 2 entries in the file one being the actual and other being the first match.

@codingo
Copy link
Owner Author

codingo commented Oct 4, 2017

Great! I think master already has the first issue resolved - I've pushed about four pr's in the last three days. You should be able to merge it back over ok.

And yup, in this case the output would automatically work since you would be popping out of the routine early (and subsequently not adding on output).

@prabhath6
Copy link
Contributor

okay, i will pull in latest changes and push out the change.

@codingo
Copy link
Owner Author

codingo commented Oct 8, 2017

Resolved in #63

@codingo codingo closed this as completed Oct 8, 2017
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

2 participants