Re: [NSE] Catching socket errors, documentation discrepancy

[Daniel Miller <bonsaiviking () gmail com>]

Specifically, trying to send on an unconnected socket. There's
probably a better way to do things in general, but I'm working with
someone else's code and trying not to make sweeping changes. A minimal
test script is attached that exhibits the behavior.

Dan

On Wed, Sep 21, 2011 at 5:26 PM, David Fifield <david () bamsoftware com> wrote:
> On Wed, Sep 21, 2011 at 05:23:25PM -0500, Daniel Miller wrote:
> > Hey list,
> >
> > While working on a script, I found that the socket I/O described on
> > the NSE API page (http://nmap.org/book/nse-api.html) and in the nmap
> > library documentation (http://nmap.org/nsedoc/lib/nmap.html#send) is
> > not how it is currently implemented. Specifically, socket operations
> > are now throwing Lua errors instead of returning a false value and
> > an error string. Is there a current reference for how errors should
> > be treated? Is there a plan to change the existing documentation to
> > match the current implementation? I could source-dive and find how
> > to do it myself, but I think we should be a little more
> > user-friendly for script authors who take the documentation at its
> > word.
>
> Please be more specific about the socket errors that are causing Lua
> errors for you. Can you show us example code?
>
> David Fifield

Attachment: test.nse
Description:

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