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

Masscan should scan target, not whitelist. #900

Closed
TheTechromancer opened this issue Dec 8, 2023 · 2 comments · Fixed by #886
Closed

Masscan should scan target, not whitelist. #900

TheTechromancer opened this issue Dec 8, 2023 · 2 comments · Fixed by #886
Assignees
Labels
bug Something isn't working

Comments

@TheTechromancer
Copy link
Collaborator

No description provided.

@TheTechromancer TheTechromancer added the bug Something isn't working label Dec 8, 2023
@TheTechromancer TheTechromancer self-assigned this Dec 8, 2023
@TheTechromancer TheTechromancer changed the title Massdns should scan target, not whitelist. Masscan should scan target, not whitelist. Dec 9, 2023
@TheTechromancer
Copy link
Collaborator Author

Questioning the reasoning behind this. I made the issue while doing internal asset inventory and I was frustrated that it was scanning the whitelist instead of the target.

The target is supposed to "seed" the scan. So it seems okay to scan it even if it's not explicitly whitelisted, because the resulting open ports will still be handled properly.

@TheTechromancer TheTechromancer linked a pull request Dec 15, 2023 that will close this issue
@TheTechromancer
Copy link
Collaborator Author

Fixed in #886.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant