mailing list archives
Re: How is whois.nse coming along?
From: Kris Katterjohn <katterjohn () gmail com>
Date: Sun, 29 Jun 2008 21:32:10 -0500
-----BEGIN PGP SIGNED MESSAGE-----
The script now uses a locally cached copy of IANA's IPv4 Global Unicast
Address Assignments  to determine which service to query by matching
the target against the assignment prefix ( nnn/8 ). The file is
currently being stored alongside nmap-services et al. since the script
uses nmap.fetchfile() to get a directory path. I wonder if anyone has
any opinions on whether this is a good or bad place to store it - it's
certainly the most convenient and should be satisfactory across all
platforms, but if Kris introduces a data directory for nselib data files
, maybe it could go there.
Maybe there can be a data directory for NSElibs and one for scripts?
Or maybe your address space parsing code can be placed in the Datafiles
library for use by other scripts, thus allowing ipv4-address-space to be
logically placed in a NSElib data directory? It's not strictly an Nmap data
file, but maybe that can slide if it's sufficiently useful.
Or, better yet, maybe it can extend the ipOps library since it's already
presenting an isPrivate() function. I recall a discussion on presenting an
ip_is_reserved()-esque function (a la nmap.cc) to scripts, and this could
present that and more.
Of course, these last two ideas could easily be beyond the scope of the code
you've already written, in which case they can be saved for the future :)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Sent through the nmap-dev mailing list
Archived at http://SecLists.Org
Re: autonomous system numbers NSE script Fyodor (Jun 29)