Nmap Development mailing list archives
Re: [NSE] Script execution error message
From: Patrick Donnelly <batrick () batbytes com>
Date: Thu, 29 Mar 2012 18:01:58 -0400
On Thu, Mar 29, 2012 at 5:55 PM, Patrik Karlsson <patrik () cqure net> wrote:
Thanks for the input Patrick. Personally, I see two scenarios here: - A script/library is crashing for every execution due to some recent changes somewhere in the code base - A script/library is crashing due to some unexpected behavior/response from a specific server service In the second case it would be very useful to track the error to the host/service triggering it without having to re-run the complete scan in verbose mode. Therefore I believe it would be better to keep the error messages individually.
Sure, that makes sense.
Ideally, we shouldn't be seeing much of these errors anyway, right?
Right. There are certain errors that are not unexpected though. For example, we had require errors for openssl that we arbitrarily silenced. In the future, we may want to add other errors which are silenced as well. They may be generic like "wrong service" (e.g. http-* scripts did not find a web server on port 80). This is, admittedly, the opposite of your problem but still something to think about. -- - Patrick Donnelly _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://seclists.org/nmap-dev/
Current thread:
- [NSE] Script execution error message Patrik Karlsson (Mar 29)
- Re: [NSE] Script execution error message Patrick Donnelly (Mar 29)
- Re: [NSE] Script execution error message Patrik Karlsson (Mar 29)
- Re: [NSE] Script execution error message Patrick Donnelly (Mar 29)
- Re: [NSE] Script execution error message Patrik Karlsson (Mar 29)
- Re: [NSE] Script execution error message Patrick Donnelly (Mar 29)