Re: How is whois.nse coming along?

[Kris Katterjohn <katterjohn () gmail com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

jah wrote:
> The script now uses a locally cached copy of IANA's IPv4 Global Unicast
> Address Assignments [1] 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
> [2], 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 :)

> Regards,
>
> jah

Thanks,
Kris Katterjohn

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQIVAwUBSGhFqP9K37xXYl36AQJsERAAoF5cHPXeX4556fRmNauS/2ElMEpJW7eF
hjIV84m5c9NDCfUIx9pUQ2azD/sytZO6hg6RjbS8nw+xLqv13Zk14cXmPh6GDjIa
MZB1CFgB7McjDMMM5jgh1rS+RQTzVia6KAtGZt3KEt9s732NW3A3a+wX33JA5E7p
t3PI46cLdWzHa06Gu4i/Qbz1bzwwrLVRsJoZ+ZH7rcQnSs3EZPXujoXVzbEZ10U7
4cilTwOb2z5SeqHGwmGsZXPnzadIBYofM06uKTnKNm0aez3cO84ADNlm2dk5aWdc
kkDytIMxg9fNhWJkTW5VCqRMzStQs4y35MDntntR2DS8bnFxF80z6JKR2uTLChGM
9yDNTBIumYl3jWWgA2Og+aBYjODU9u35ttij/F2l60unaHmrwZnq7Kr0uTptFFet
6G3XLoi+CEnMhGhTLlaT+OcaXes4VvOkPuiBSMHgCzOWTv1FbCyCHcbWhfJOEovy
6grcTqmr4e2cfxABZl9c+qVzmuwIxtU3buuYJXqW2J7CxmqEgEaYfkpm4LHr0D7U
KqjiStebD15F9Dv9yNq9FpdDdMJNU73TGxQlI6QF5gvGqDmWwlXqhQCXV0cYEx6r
MecDkQecqn2rD57QTgo6fopgfu3AruEfKtM0q7aWrAGsGFCy1nC5EJXJkS4rtpZb
awLi5ErgMco=
=jlEK
-----END PGP SIGNATURE-----

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org