mailing list archives
Re: [RFC][PATCH] NSE version numbering
From: Ron <ron () skullsecurity net>
Date: Mon, 11 Apr 2011 10:56:54 -0500
-----BEGIN PGP SIGNED MESSAGE-----
So, this might be a silly idea, but...
On Mon, 11 Apr 2011 16:43:33 +0100 Djalal Harouni <tixxdz () opendz org> wrote:
Of course we can also add hooks to catch any call to unsupported
functions, print a message to the user that he should report this to
nmap-dev or update his Nmap/NSE core ..., and then clean and
terminate the script/thread, this way other scripts can continue
Why don't we just do that, and nothing else? Basically, catch all calls to unsupported functions, print a warning that
the function doesn't exist and that they should update Nmap to use this script, and that's it?
It's a stupidly easy solution, Nmap doesn't crash, the scripts that can run still run, and life is good.
Is the extra complexity of knowing beforehand really worth it?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
-----END PGP SIGNATURE-----
Sent through the nmap-dev mailing list
Archived at http://seclists.org/nmap-dev/