Re: Some scripts for analyzing NetBus

[Toni Ruottu <toni.ruottu () iki fi>]

To this mail, I have attached a patch that should fix all the netbus
script problems that have been pointed out. I noticed that sometimes
dns-zone-transfer.nse breaks the session. As we know now NetBus
sessions are very fragile. Running any other scripts that operate on
the same port simultaneously is very likely to break the server. I did
not include a fix for this problem in the patch as I was not sure what
to do. Should we have all scripts that match port 12345 depend on all
netbus scripts? I also did not change any categories, as the question
is still open.

On Fri, Jan 14, 2011 at 10:45 AM, Fyodor <fyodor () insecure org> wrote:
> On Thu, Dec 30, 2010 at 02:37:38PM +0200, Toni Ruottu wrote:
> > > > The scripts store a password in nmap.registry.netbuspassword. This won't
> > > > work if more than host with different passwords is scanned at the same
> > > > time. You should make this indexed by IP address and port number.
> >
> > Is string.format("%s:%d", host.ip, port.number) always unique and a
> > valid key, or is there some advanced library function for serializing
> > the host information? E.g. what would happen if the host was IPv6?
>
> When you add that and the <empty> thing David mentioned, could you
> also add an NSE script argument for specifying the Netbus password for
> scripts like netbus-info?  That way users don't need to use
> netbus-brute every time.  It would then need @args to be documented in
> the NSEDoc section.  See Patrik's informix-query (among many other
> scripts which do this) for an example of passing the authentication in
> a script arg.  And would you add a @usage section to the scripts where
> the default generated by our NSEDoc renderer "nmap -sV
> --script=[scriptname] <target>" isn't ideal or informative enough?
>
> I'm glad the new Nmap release will have some old school protocols like
> Gopher and Netbus thanks to your scripts :).
>
> Cheers,
> Fyodor

Attachment: netbus-improvements.patch
Description:

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