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

Giving rustscan specific ports to scan #85

Closed
idangur opened this issue Jul 30, 2020 · 3 comments · Fixed by #158
Closed

Giving rustscan specific ports to scan #85

idangur opened this issue Jul 30, 2020 · 3 comments · Fixed by #158

Comments

@idangur
Copy link

idangur commented Jul 30, 2020

I think it will be really benefitial for me and surely for other people to list specific ports
for rustscan to scan, as a way to reduce network output of both nmap and rustscan.

Maybe as a json file argument or as an argument type, something like 21-23,80,443,445,700-1024,
Just a thought and maybe i can check at how it can be implemented if wanted as a feature.

And i just wanted to say that the project can grow to be so much more and has a lot of potential!!!

@bee-san
Copy link
Member

bee-san commented Jul 30, 2020

Hey!!!

Thanks for your kind words :D

I'm planning on adding port ranges, maybe in JSON format;
Something like:

IP: 80, 443, 8080
CIDR rane: 1-65535

So users can control exactly what gets scanned from what IP addresses :D

Right now I'm rewriting how we deal with IP addresses, and then I'll add CIDR support and eventually individual port support :)

@bernardoamc
Copy link
Collaborator

Somehow I think this would fit really well in a toml file format akin to our Cargo.toml. What do you think? :)

@bee-san
Copy link
Member

bee-san commented Jul 31, 2020

Somehow I think this would fit really well in a toml file format akin to our Cargo.toml. What do you think? :)

Perfect! I'll move it over there :D

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

Successfully merging a pull request may close this issue.

4 participants