Nmap Development mailing list archives

Re: LAN/WAN Configuration Management


From: magnus () linuxtag org (Nils Magnus)
Date: Mon, 3 Oct 2005 20:52:36 +0200

Re,

On Mon, Oct 03, 2005 at 02:29:09PM -0400, Fred Eisele wrote:

I would like to see a stronger xml presence in nmap, as I feel that would
make it easier to integrate nmap into such a mechanism
In particular, I would like to see/develop...
- some nice graphical output (in svg)

I'd love to see something like that as well, but don't underestimate the
comlexity of such a task. In fact this applies to several of your
suggestions: In my opinion, one of the key factors for nmap's success is
the very general approach; nmap does not make much assumptions about the
environment it scans.

If you try to draw network maps automatically, usually they are not much
better help compared to the text form, since graph placing/routing seems
to be a rather complex task. However, I do not intend to keep you from
developing something like that.

Have you considered making use of a "proper" xml dom
library (e.g. libxml2, xerces) rather than the roll-your-own technique?
This could make the -append-output problem quite a bit easier to handle.

Well, that is right, but earlier discussion also showed that some people
like the XML approach, but some don't use that at all. Again, I am not
sure if sacrificing part of that generalistic approach is a good idea.

We are alredy at a point where complexity is obviously an issue for
nmap, even in the core functionality. I those propose to implement such
ideas "around" the vanilla nmap.

It would be helpful if the master file described certain missing information.
For example, the routing tables.
Anyway, the question, I guess, is whether nmap could use that information
to do a better job of scanning?

Hm, effectivly nmap just distinguishes between layer-2 connected and
layer-3+ connected networks. To assess information about some network
infrastructure, the routing table and other stuff you usually asses with
traceroute/tcptraceroute etc. is very helpful, if not crucial for such
tasks. It is very tempting to try to integrate that information into
nmap, but the complexity threat comes quickly in there, again.

Regards,

Nils Magnus
Program-Chair LinuxTag 2005 Free Conference Program

LinuxTag 2005: Where .com meets .org - magnus () linuxtag org


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


Current thread: