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

feat(scan): Improve internal network scan #125

Open
3 tasks done
psyray opened this issue Jul 8, 2024 · 0 comments
Open
3 tasks done

feat(scan): Improve internal network scan #125

psyray opened this issue Jul 8, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@psyray
Copy link
Contributor

psyray commented Jul 8, 2024

Expected feature

I've scanned my home network.

It misses a prebuilt scan engine for this
subdomain discovery is useless, OSINT also
image

There also a little problem

  1. We add an internal range
  2. We check the hostname we want
  3. We have multiple target
  4. We want to print report, we need to check on each target -> pain ....
    And 1 report by target

What about adding hostnames/ips found to a target as subdomain ?
This one need some work I think, because there's some checks for the target owning the sub (domain name)

For this one maybe let the user choose, with a choice like "Import each IP/hostname as a target" or "Import each IP/hostname as a subdomain of the given target" with a text field saving the target name

But the problem of subdomain not member of a TLD is problematic
It's a different way to manage target, at local domain level.

If it's an active directory no problem we could add the domain name (> 4 chars when #9 will be merged)

But if it's a network without a domain it's problematic

Maybe set an option at the target level to deactivate the restriction on the TLD

Alternative solutions

No response

Anything else?

No response

Acknowledgements

  • This issue is not a duplicate of an existing bug report.
  • I have chosen an appropriate title.
  • All requested information has been provided properly.
@psyray psyray added the enhancement New feature or request label Jul 8, 2024
@psyray psyray added this to the v2.1.0 release milestone Jul 8, 2024
@psyray psyray modified the milestones: v2.1.0 release, v2.2.0 release Aug 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant