Closed ozkanpakdil closed 2 years ago
write port scanner feature for frizz, get the parameters from CLI parameter
frizz -p from_port-to_port -t targethost_or_ip example
frizz -p 22-1024 -t google.com
make sure port scanner works multi threaded, open threads count of CPU e.g:8 this can be given from CLI example
frizz -tc 16 -p 22-1024 -t google.com £ which will open 16 threads
check nmap usage examples https://techtalk.gfi.com/scanning-open-ports-in-windows-part-3-nmap/ which has been around like 20 years, try to use same parameter names on CLI just for being user friendly.
at the end, test and compare nmap with frizz to see speed differences.
TODO:
4 sub issue created to fix this issue.
write port scanner feature for frizz, get the parameters from CLI parameter
frizz -p from_port-to_port -t targethost_or_ip example
frizz -p 22-1024 -t google.com
make sure port scanner works multi threaded, open threads count of CPU e.g:8 this can be given from CLI example
frizz -tc 16 -p 22-1024 -t google.com £ which will open 16 threads
check nmap usage examples https://techtalk.gfi.com/scanning-open-ports-in-windows-part-3-nmap/ which has been around like 20 years, try to use same parameter names on CLI just for being user friendly.
at the end, test and compare nmap with frizz to see speed differences.