Opened 11 years ago
Closed 11 years ago
#4974 closed enhancement (fixed)
nmap-6.46
Reported by: | Fernando de Oliveira | Owned by: | Fernando de Oliveira |
---|---|---|---|
Priority: | normal | Milestone: | 7.6 |
Component: | BOOK | Version: | SVN |
Severity: | normal | Keywords: | |
Cc: |
Description ¶
http://nmap.org/dist/nmap-6.46.tar.bz2
http://nmap.org/changelog.html
Nmap 6.46 [2014-04-18] o [NSE] Made numerous improvements to ssl-heartbleed to provide more reliable detection of the vulnerability. o [Zenmap] Fixed a bug which caused this crash message: IOError: [Errno socket error] [Errno 10060] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond The bug was caused by us adding a DOCTYPE definition to Nmap's XML output which caused Python's XML parser to try and fetch the DTD every time it parses an XML file. We now override that DTD-fetching behavior. [Daniel Miller] o [NSE] Fix some bugs which could cause snmp-ios-config and snmp-sysdescr scripts to crash (http://seclists.org/nmap-dev/2014/q2/120) [Patrik Karlsson] o [NSE] Improved performance of citrixlua library when handling large XML responses containing application lists. [Tom Sellers]
Change History (3)
comment:1 by , 11 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:2 by , 11 years ago
Note:
See TracTickets
for help on using tickets.
Every time, the same tests fail. Identical results either as root or regular user.
Now, I can understand that two of them are wrong and I can fix them. First, zenmap_check, by removing a "dot" in Makefile.in. Second, ndiff_check, by removing attribute "StringIO" from "StringIO" in ndiff/ndifftest.py (whatever that means).
Five "subtests" from ncat_check are expected to fail, but don't do it. I cannot say that I understand enough to state that they are wrong. But I can just remove 5 "expect_fail" addresses from ncat/test/test-addrset.sh.
Thus, "make check" can be run without error, with the patch:
Is it worth to include this patch in the build?
I will not update this today. Will leave for tomorrow.