Nmap Development mailing list archives

Re: Zenmap not terminating properly on Windows


From: Nick Marsh <goaliefight () gmail com>
Date: Thu, 20 Aug 2009 04:10:45 -0500

One thing to keep in mind here is that I didn't kill Zenamp. It was a clean
exit. Also, I clicked the cancel button which SHOULD have terminated the
subprocess regardless of weather or not I closed Zenamp.

Nick


On Wed, Aug 19, 2009 at 6:56 PM, David Fifield <david () bamsoftware com>wrote:

On Fri, Aug 14, 2009 at 11:52:51AM -0500, Nick Marsh wrote:
Today I was running the Nmap 5.0 package on Windows Vista (SP2 - 64-bit)
and
performed a Zenmap "quick scan plus" on 10.10.1-12.1-10.

I canceled the scan and closed Zenmap when I discovered that it was
DOSing
my firewall/router/ids. After closing Zenmap I continued to have
problems.
In viewing the logs on my firewall/router/ids it appeared that my machine
was still actively scanning even though Zenmap was closed.

I had to reboot my PC to make it stop. I'm not too concered about it, but
I
wanted to let you know. BTW I'm new here so I hope this isn't a duplicate
report.

I think this has the same cause as the problem with & in a file name on
Windows reported in http://seclists.org/nmap-dev/2009/q3/0604.html,
namely, that on Windows the Nmap subprocess is spawned with shell = True.
This done to avoid having a terminal window open every time you run a
scan in Zenmap, but as a side effect it means that when the subprocess
is killed, it only kills the shell and not the nmap process that is
running in the shell.

Does someone have an idea of how to solve this? Is there a Python way to
run a terminal program without opening a terminal window? To see what I
mean, edit zenmapCore/NmapCommand.py and change the line

shell_state = (sys.platform == "win32")

to

shell_state = True

David Fifield


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


Current thread: