-
Notifications
You must be signed in to change notification settings - Fork 18
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
Unlikely to Support UDP Port Scan #14
Comments
I think to successfully do a UDP port scan, you may need a list of pre-determined list of services to probe for responses. I understand this is a lot of work so I'm just putting this out there for reference. I don't think I can do this on my own :D |
You are probably right with the UDP support. I honestly added it as a throwaway feature since:
|
Just a cursory look at the implementation of the code, I reckon the UDP port scan would not work just because of how UDP protocol works. If the the code dials the target with UDP protocol e.g.
conn, err = net.Dial("udp", raddr)
, there will not be any error message from the target server just because UDP is connectionless. A server will only reply when a "meaningful" packet is sent to the UDP port on the target. For more info - https://serverfault.com/a/416269By the current way of checking for open/close UDP port i.e. presence of error dialing the target, all UDP ports would be open. Which defeats the purpose of a port scan.
Alternatively, can refer to how
nmap
implements its UDP probe - https://nmap.org/book/scan-methods-udp-scan.htmlThe text was updated successfully, but these errors were encountered: