Home page logo
/

nmap-dev logo Nmap Development mailing list archives

Re: nmap bug report
From: "ka hoi ng" <khng.email () gmail com>
Date: Sun, 11 May 2008 11:51:55 +0800

Thanks you for the timely response.

I have followed the instruction from the email and it works great.

But I would like to report some bugs associated with the zenmap

   - The "Save Scan" Function don't work on non-english version of window
   (as can't be opened by zenmap again)
   - The Command field under the Target and and in "Command Info " of "Scan
   Details" don't reflect the real command that was executed in the saved scan
   (It always show the definition of the defined profile, but ignoring the
   modification by the user at execution, that should be fixed by reading the
   args attribute in the nmaprun tag inside the xml file)



On Sun, May 11, 2008 at 4:07 AM, David Fifield <david () bamsoftware com>
wrote:

On Sat, May 10, 2008 at 09:23:35PM +0800, ka hoi ng wrote:
Version: 4.62
OS: Windows XP Pro Service Pack 3
Symptom: Can't Open File Saved by non-english OS (e.g. Traditional
Chinese)
Gtk-ERROR **.file:../../../gtk+/gtk/gtktextsegment.c: line 196
(_gtk_char_segment_new): assertion failed (gtk_text_byte_beings_utf8_char
(text)) absorting

Attached was two scan result using the same option but on different
language
of Windows XP (TC=Traditional Chinese, EN=English)

Thanks for your report. I can verify that the EN_OS.usr file opens and
the TC_OS.usr causes a crash. Both files are written with an XML
declaration that declares an ISO-8859-1 encoding:

   <?xml version="1.0" encoding="iso-8859-1"?>

That comes from these few lines in zenmapCore/NmapParser.py:

   def write_xml(self, xml_file):
       xml_file = self._verify_file(xml_file)
       self.write_parser = XMLGenerator(xml_file)

where the encoding of the XMLGenerator defaults to "iso-8859-1" (see
http://docs.python.org/lib/module-xml.sax.saxutils.html#l2h-1924).

I think it's the time zone in the XML output that's not encoded in
ISO-8859-1. Maybe this can be fixed just by changing the output
encoding.

Run your scan again, like this:

   nmap -T Aggressive -sV -n -O -v 192.168.1.142 -oX TC_OS.xml

and then try to open the TC_OS.xml file in Zenmap. If it works, then the
problem probably lies with Zenmap rather than Nmap.

David Fifield




-- 
The above message is encoded in UTF-8
If can't see that, then please do the following steps in order to display
the message;

For Internet Explorer,
1. Select View (alt-v)
2. Select Encoding (d)
3. Click Unicode (UTF-8)

For Mozilla/FireFox,
1. Select View (alt-v)
2. Select Character Encoding (c)
3. Click Unicode (UTF-8)

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


  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]