-
Notifications
You must be signed in to change notification settings - Fork 182
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
Fails to parse nmap data of osclass tag #26
Comments
yep. this changed in nmapv6. in nmapv5 it is on the same "level". There is already a bug filed for this. I'll try to fix it this week along with issue #25 both should be quickly fixed. Thanks for bug reporting. |
this is the explanation from the nmap-dev mailing list. I will base the fix on this input from nmap's devs http://seclists.org/nmap-dev/2012/q2/252 I will probably do the nesting by accuracy matching when osclass is not nested and still have untied osclass array internally. |
approach for solving this out create an osmatch class which will contain:
this approach will also close issue #11 |
fixed in commit 01096b4 |
Hi :
When the nmap scan OS, my output is follow:
the
<osclass>
is under<osmatch>
but i see theparser.py
like this:I think you handle
<osclass>
and<osmatch>
in a same level.So the
NmapHost.os_class_probabilities()
has no resultMy nmap version is:
I'm not sure whether the nmap version problem
Thinks 😄
The text was updated successfully, but these errors were encountered: