-
Notifications
You must be signed in to change notification settings - Fork 53
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
Add more ports to stage 7 #80
Comments
I suggest adding the standard TCP ports of commonly used databases:
References: For a complete port scan specialized tools like nmap should be used. I think to work out a tiny list of typical falsely open ports on web servers should be the aim for the twa script. |
That sounds good to me. I've been on the fence about which ports to add, since |
@woodruffw |
@GatewayBit go for it! |
The issue is more than one month open. I add the ports now to the source. |
@UlrichBerntien Go ahead with this task. Thank you! |
* add more ports to scan in stage 7, see issue #80 * add port number comment to message output * fixed grammar nit: listen -> is listning Co-authored-by: UlrichBerntien <UlrichBerntien@users.noreply.github.com>
I think #85 covers the majority of the ports I had in mind, so I'm going to close this. We can address additional ports/changes in subsequent issues and PRs. |
There are lots of other common development ports that we should check for, including (but not limited to):
5000
(Flask and Kestrel's default port)9200
(Elasticsearch's REST API)The text was updated successfully, but these errors were encountered: