-
Notifications
You must be signed in to change notification settings - Fork 60
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
Service name inference by port in kat_nmap normalizer #2037
Comments
No, then it should not be overwritten bij http or https. I remember a thing where nmap would identify services like http-web instead of http. Maybe this was implemented to overwrite those...? |
Could very well be, nmap reports the following http type service names:
We could opt for a simplified re-classification where suited?
See this comment for more background. |
Sounds better to me |
Addressed in 78a830e. It is better to use tunnel type in stead of service name as that is the format used in the XML output (rather than the standard output). |
Question regarding the following lines of code:
nl-kat-coordination/boefjes/boefjes/plugins/kat_nmap/normalize.py
Lines 46 to 50 in 56c8004
Suppose one places a
ssh
server behind port 80 or port 443, do we really want to reporthttp
orhttps
respectively?Perhaps there are considerations for this behavior?
The text was updated successfully, but these errors were encountered: