Re: Interacting with scan can break XML DTD validation

[Daniel Miller <bonsaiviking () gmail com>]

On 09/02/2011 04:39 PM, David Fifield wrote:
> Good find. I think this is a problem with the DTD, specifically the
> (taskbegin, taskprogress*, taskend) part. It's hard to enforce ordering
> and number of elements like this. Can you try just folding those into
> the rest of the unordered elements, and if that works, send the patch
Here is that patch. It works, and I don't have a problem with being a 
little more lax on this. I do think it would be good to output 
information about changes in verbosity and debug level, if they change 
the XML output, but that will take a little more time to hunt down and 
investigate.

Dan

Attachment: dtd.patch
Description:

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