On Fri, Nov 08, 2002 at 08:06:11AM -0500, Max Schubert wrote:
> info for event-driven APIs ... mine is in perl and is at
>
> http://webwizarddesign.com/nmap/
>
> But is only works with a given nmap version as the LOG_STDOUT
> output has changed between versions :( .. and the parsing is
> complex and breaks easily .. blech.
I agree that parsing Nmap XML output is the way to go. I believe that
approach is even better than the SO/DLL suggestion on your web page.
I have applied your patch for the next version of Nmap, which I hope
to release in the next few days. Your patch is reversed, but that
doesn't really matter. For consistancy with other Nmap XML elements,
I changed the tag name to 'addport' and the 'number' parameter to
'portid'. I also removed the 'msg' parameter. I updated the
docs/nmap.dtd to recognize this new tag.
Please let us (nmap-dev or nmap-hackers) know once your parser is
working with XML output. It would be nice to see more code examples
of Nmap XML parsing.
Cheers,
Fyodor
---------------------------------------------------------------------
For help using this (nmap-dev) mailing list, send a blank email to
nmap-dev-help_at_insecure.org . List run by ezmlm-idx (www.ezmlm.org).
Received on Nov 08 2002
Intro
