A strange bug is causing the port scan results to be outrageous.
Open
bug
- Dominant language
- Rust
- Stars
- 20.4k
- Forks
- 1.4k
- PR merge metrics
- No merged PRs in 30d
Description
1.If I use the --range command to limit the port range, I am still unable to discover open ports even when scanning at a very slow rate
2.If I use the -p command to specify the port, then I am able to discover open ports.
RustScan is a great tool with ambitious goals, but this scanning issue is indeed quite strange.
Contributor guide
Assessment
This issue has not been assessed yet.