Nmap Development mailing list archives
[Zenmap] Terminal Problem due to Nmap Runtime Interaction
From: Jay Bosamiya <jaybosamiya () gmail com>
Date: Mon, 16 Jun 2014 15:48:38 +0530
Hi All! If I were to open Zenmap from terminal, and then Cancel a running scan, then the terminal is in an unusable state (typed characters are not echoed after closing Zenmap). I am forced to close the terminal and open a new one. This is caused because a SIGKILL is sent to Nmap when we cancel a scan. I think that this should be a SIGTERM so as to allow for a clean shutdown. Attached is a patch that does this. Note: There is runtime interaction when you run Zenmap from terminal. You can notice this by pressing keys on the terminal when a scan is running. I think that there should *not* be any runtime interaction in this case. Since not a lot of people run Zenmap from terminal, I think it'd be a low priority but should probably be done at some point of time in the future. Cheers, Jay
Attachment:
zenmap_terminal_nice_shutdown.patch
Description:
_______________________________________________ Sent through the dev mailing list http://nmap.org/mailman/listinfo/dev Archived at http://seclists.org/nmap-dev/
Current thread:
- [Zenmap] Terminal Problem due to Nmap Runtime Interaction Jay Bosamiya (Jun 16)
- Re: [Zenmap] Terminal Problem due to Nmap Runtime Interaction Jay Bosamiya (Jun 26)
- Re: [Zenmap] Terminal Problem due to Nmap Runtime Interaction Jay Bosamiya (Jun 26)
- Re: [Zenmap] Terminal Problem due to Nmap Runtime Interaction Daniel Miller (Jun 27)
- Re: [Zenmap] Terminal Problem due to Nmap Runtime Interaction Jay Bosamiya (Jun 26)
- Re: [Zenmap] Terminal Problem due to Nmap Runtime Interaction Jay Bosamiya (Jun 26)
