Nmap Development 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----- Hash: SHA1 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 running.
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? Ron -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iEYEARECAAYFAk2jJMoACgkQ2t2zxlt4g/SdugCgpe927OilFg9NcP5XMZvzjRxf +PkAoJfEfD2hvMkAgQnOA0V1qM/5/igc =lQPY -----END PGP SIGNATURE----- _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://seclists.org/nmap-dev/
Current thread:
- Re: [RFC][PATCH] NSE version numbering Ron (Apr 03)
- Re: [RFC][PATCH] NSE version numbering Djalal Harouni (Apr 11)
- Re: [RFC][PATCH] NSE version numbering Ron (Apr 11)
- Re: [RFC][PATCH] NSE version numbering Djalal Harouni (Apr 11)