Skip Menu |

This queue is for tickets about the Nmap-Parser-XML CPAN distribution.

Report information
The Basics
Id: 5139
Status: resolved
Worked: 10.1 hours (603 min)
Priority: 0/
Queue: Nmap-Parser-XML

People
Owner: apersaud [...] cpan.org
Requestors: cjs [...] dhp.com
Cc:
AdminCc:

Bug Information
Severity: Critical
Broken in: 0.71
Fixed in: 0.71



Subject: xml declaration not at start of external entity
I get the following type of errors when trying to parse through nmap output: xml declaration not at start of external entity at line 131501, column 0, byte 9124127 at /usr/local/lib/perl5/site_perl/5.8.2/mach/XML/Parser.pm line 187 This is happening on most of my xml output files..
[guest - Fri Jan 30 16:42:18 2004]: Could you be a little more specific? Was it during installation? Was it using parsescan()? an example script? Could I see the start of your nmap-xml output files? Please use this site: http://www.sourceforge.net/projects/npx/ for any more bugs. Thanks, Anthony I've placed your bug on the Sourceforge tracker: http://sourceforge.net/tracker/?atid=618345&group_id=97509&func=browse Show quoted text
> I get the following type of errors when trying to parse through nmap > output: > > xml declaration not at start of external entity at line 131501,
column Show quoted text
> 0, byte 9124127 at > /usr/local/lib/perl5/site_perl/5.8.2/mach/XML/Parser.pm line 187 > > This is happening on most of my xml output files..
After running various tests, it seems that my hypothesis was right. If you are piping the output and one of the machines (computers) makes nmap go crazy, it will spit back non-xml or incorrect markup causing the parser to fail. Other times, even scanning and saving the xml output to a file, will cause the XML file to be incomplete -- which causes the parser to fail. I say, please test your network by running 'nmap -sT -oX - ip.ip.ip.ip/mask' or whatever was the scan options, and see if you get an incomplete xml file.