Nmap Development mailing list archives

Re: Allow for disabling port grouping (with something more clear than debug level 2)


From: Daniel Miller <bonsaiviking () gmail com>
Date: Wed, 4 Mar 2015 07:51:20 -0600

Klondike,

Thanks for your interest and the suggestion. We have discussed in the past
[1] how collapsing based on port state is missing information about the ttl
of any responses (e.g. one port could be blocked by a firewall, and another
by the host, but both would be collapsed into one "extraports" element,
even though the responses have different TTLs). While this is not directly
related to your suggestion, it is an issue that touches some of the same
functions you would have to modify in order to support your suggestion, and
may interest you.

I look forward to seeing how you tackle the problem! Please do subscribe to
the list, since that will allow your messages to be immediately posted
without going through moderation.

Dan

[1] http://seclists.org/nmap-dev/2014/q3/93

On Wed, Mar 4, 2015 at 3:21 AM, klondike <klondike () klondike es> wrote:

Hi dear nmap hackers!

First of all thanks a lot for such a nice tool, it has saved my ass
debugging network issues quite a few times :)

I'm writing you because for some uses port grouping can be problematic
when parsing outputs (specially if more than one group is created).
Initially I was just thinking on patching PortList::isIgnoredState(int
state) on portlist.cc with a simple new option to disable grouping, but
I suppose there are other needs too aside from just enabling/disabling
grouping for all states.

And this is the reason of this e-mail, I have to write this feature, I'd
like it to be merged with nmap and I believe it will be nice if it is of
help to as many users out there. So please send your ideas (and please
CC me as I'm not subscribed to this list).

Sincerely,
klondike


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

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

Current thread: