On Sat, Nov 07, 2009 at 07:23:43AM -0500, Ron wrote:
> Fyodor wrote:
> > On Fri, Nov 06, 2009 at 10:13:46AM -0500, Ron wrote:
>
> > Maybe it should include a stopafter limit by default? That way it
> > doesn't go forever for people who acidentally specify it (perhaps
> > among other scripts) without specifying the stopafter arg.
> Sure, any suggestions on how long it should go for?
Maybe 1MB per service?
> > Also, you might want to make this output line more clear:
> > return false, string.format("Finished sending data: %s (%d bytes already sent)", err, amt)
> >
> > You might want to note that it failed to send more data and thus the
> > service may have crashed. Otherwise it looks pretty similar to the
> > successful finish case:
> >
> > return false, string.format("Finished sending data: %s (%d bytes already sent)", err, amt)
> I'll revisit the language.
You made a good point that most services will close the connection
quickly when they receive garbage, so I suppose we don't need to
really sound an alarm. But it would be nice to note that the remote
host closed the connections and maybe you could put the number of
bytes sent and received before it closed.
A neat option (probably non-default) might be to connect back of the
remote side closes the connection. That way you can report if the
service has completely crashed.
Cheers,
-F
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-devArchived at
http://seclists.org/nmap-dev/
