Nmap Development mailing list archives
Re: Zenmap broken XML parsing
From: David Fifield <david () bamsoftware com>
Date: Mon, 27 Jul 2009 15:24:30 -0600
On Wed, Jul 22, 2009 at 09:51:04PM +0430, Hamid Kashfi wrote:
## and second problem , Zenmap XML parsing : Zenmap seems to fail reading XML files that are result of incomplete scans ( like ended by ctrl+x ) or even XML files being appended by --resume . Is fixing the xml mess manually , the only way to have outputs back in Zenmap ?
Interrupting a scan or appending an XML scan to half of an existing XML scan is going to leave a broken XML file. I'm not sure it's worth Zenmap supporting this. Your web browser and any other XML tool is going to reject it too. It might be reasonable to support parsing an interrupted XML file, if it's possible to get the Python XML parsing libraries to reveal what is the cause of an XML parsing exception. Appending a new root element to a half-completed XML file (as --resume does) leaves a thoroughly mixed-up document; that's not likely to be supported. David Fifield _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://SecLists.Org
Current thread:
- nmap --resume problem // Zenmap broken XML parsing Hamid Kashfi (Jul 25)
- Re: nmap --resume problem David Fifield (Jul 27)
- Re: Zenmap broken XML parsing David Fifield (Jul 27)