How about doing some diff's on OS's in the O1 and O2 and then creating
priority hit lists for submission into the new release? With a email
list like nmap-dev we could probably fill in those missing 857
fingerprints in short order. Or atleast narrow it down. I can see the
value in an obscure os id.
On 10/28/07, Fyodor <fyodor_at_insecure.org> wrote:
> 1st generation Nmap OS detection had a great run, lasting 9 years.
> But now that the 2nd generation DB has grown considerably, it may be
> about time to let gen1 OS detection go. It complicates the code, and
> the gen1 DB itself takes up more than 800K of space.
>
> Then gen2 system still only has 827 fingerprints compared to 1684 in
> gen1. But the new system has better fingerprints, and for more recent
> and relevant system.
>
> So gen1 OS detection will probably be gone in the next release unless
> I hear from people who can demonstrate good reasons for it to stay.
> If you scan large networks and find that -O1 still works better than
> -O2, that's the sort of thing we'd like to hear.
>
> Cheers,
> -F
>
> _______________________________________________
> Sent through the nmap-dev mailing list
> http://cgi.insecure.org/mailman/listinfo/nmap-dev
> Archived at http://SecLists.Org
>
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org
Received on Oct 29 2007