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.

Sign up for GitHub

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

Jump to bottom

Nmap should consume IP_RANGE #877

Closed
TheTechromancer opened this issue Nov 28, 2023 · 1 comment · Fixed by #886
Closed

Nmap should consume IP_RANGE #877

TheTechromancer opened this issue Nov 28, 2023 · 1 comment · Fixed by #886
Assignees
@TheTechromancer
Labels
enhancement New feature or request

Comments

@TheTechromancer
Copy link
Collaborator

If you specify more than 65535 targets, our warning message indicates that IP_RANGE --> IP_ADDRESS speculation will be disabled, and recommends enabling a port scanner such as nmap. However, nmap does not consume IP_RANGEs. This presents a serious gap in the BBOT scan, since most of the IP addresses will never be scanned.
@TheTechromancer TheTechromancer added the enhancement New feature or request label Nov 28, 2023
@TheTechromancer TheTechromancer self-assigned this Nov 28, 2023
@TheTechromancer TheTechromancer linked a pull request Nov 29, 2023 that will close this issue
Portscanner Rework #886
Merged
@TheTechromancer TheTechromancer mentioned this issue Nov 29, 2023
Merged
@TheTechromancer
Copy link
Collaborator Author

Added in #886.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@TheTechromancer TheTechromancer

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Portscanner Rework blacklanternsecurity/bbot
1 participant
@TheTechromancer