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

unknown flag: --screenshot-filter #264

Open
bucketcat opened this issue Nov 16, 2024 · 1 comment
Open

unknown flag: --screenshot-filter #264

bucketcat opened this issue Nov 16, 2024 · 1 comment

Comments

@bucketcat
Copy link

Describe the bug
The flag for filtering HTTP response codes is missing in release 3.0.5. It is also missing in the gowitness scan file --help.

The functionality was added in this commit and discussed in this issue

On Linux, at least in the gowitness Bbot module, only HTTP 200 responses are saved to disk. The windows binary however is saving many undesirable response codes. When iterating through massive domain lists, this becomes problematic.

To Reproduce

Run gowitness scan file -f <file> --screenshot-path <path> --screenshot-fullpage --screenshot-filter <codes>

Expected behavior
The flag should exist and be recognized. It should also exist in --help.

Version Information:

  • Windows
  • gowitness 3.0.5
@bucketcat bucketcat changed the title unknown flag: --screnshot-filter unknown flag: --screenshot-filter Nov 16, 2024
@leonjza
Copy link
Member

leonjza commented Nov 17, 2024

Ah, a useful feature I missed in the v3 rewrite. Will add it back! Thanks for the report.

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

No branches or pull requests

2 participants