duplicate DLL files to the distribution. David found that using a
different GTK download fixed the problem (see
docs/win32-installer-zenmap-buildguide.txt) and Fyodor was able to
reproduce and implement.
SCRIPT ENGINE (506.424s): ./scripts/pop3-capabilities.nse against a.b.1.47:995
ended with error: ./scripts/pop3-capabilities.nse:32: bad argument #1 to
'pairs' (table expected, got string)
which happens because pop3.lua returns a string error message instead of a table
of capabilities if it can't connect the socket or obtain a response from a
connected socket.
It now returns nil, err_message in these cases and the documentation now reflects
this - pop3-capabilities.nse silently returns and prints a debug message.
Added a 10s timeout for the socket in pop3.lua capabilities - 30s was a bit much.
is that the highlight settings are not updated when Zenmap is upgraded. They
are stored in zenmap.conf, a per-user configuration file that is installed once
and not upgraded thereafter. Once someone has installed an old version of
Zenmap with broken highlighting, upgrading won't fix it unless they remove
their zenmap.conf.
the same as are used to decide whether to print them in the other
formats. So they will be printed if submission is desirable,
otherwise they are only printed if debuging is enabled or verbosity
is 2 or higher. [Tom Sellers]
because autoconf 2.63 now inserts an ac_cr definition which confuses svn
and causes this error message:
svn: File 'configure' has inconsistent newlines
svn: Inconsistent line ending style
avoid a race condition. "make all" would make nsock and ncat, and ncat
would in turn make nsock. If the timing was right, the two simultaneous
builds would trample each other.
It may seem inefficient to have all these recursive makes calling down
the dependency tree all the time, but GNU Make at least remembers which
targets were already completed so for example only one descent into
nbase_build will be done per "make all".
XML file, do "nmap 0 -oX -", not "nmap nonexistent -oX -". The first is an
invalid host specification, the second is just a name resolution error. The
original recipe was wrong in the log of the commit that fixed the problem.
exception message rather than the whole exception tuple. This changes
./ndiff: ('option --foo not recognized', 'foo')
to
./ndiff: option --foo not recognized
