PenTest/nmap
1
0
Fork 0
mirror of https://github.com/nmap/nmap.git synced 2025-12-31 03:49:01 +00:00
Code Issues Projects Releases Wiki Activity

Catch Zenmap's MemoryError (caused by large Nmap Output) and provide the user a more useful error message so that we get less of the out-of-memory "crash reports"

Browse Source
This commit is contained in:
jay
2014-07-01 16:53:10 +00:00
parent 0066d3b24e
commit 2b30085d90
4 changed files with 57 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
todo/done.txt
View File

@@ -1,5 +1,13 @@
DONE:
o In an ideal world, Zenmap would not run out of memory and crash.
And we already have an entry for improving Zenmap's memory
consumption. But in the meantime, we should catch the error and
present a more useful error message/explanation so the user
understands the problem. This should reduce the number of
out-of-memory "crash reports" we get too. See
http://seclists.org/nmap-dev/2014/q2/298
o Provide an option to send a comment in scan packet data for target
network. Examples: --data-string "Scan conducted by Marc Reis from
SecOps, extension 2147" or --data-string "pH33r my l3eT

7
todo/nmap.txt
View File

@@ -55,13 +55,6 @@ o GSOC 2014 student Jay will be looking at these items:
commonly get error reports from people who load so many systems that
Zenmap gives an out of memory error and crashes. For example, see
this thread: http://seclists.org/nmap-dev/2014/q2/46
o In an ideal world, Zenmap would not run out of memory and crash.
And we already have an entry for improving Zenmap's memory
consumption. But in the meantime, we should catch the error and
present a more useful error message/explanation so the user
understands the problem. This should reduce the number of
out-of-memory "crash reports" we get too. See
http://seclists.org/nmap-dev/2014/q2/298
o Consider using a binary decision diagram for --exclude list to make
it more efficient for large exclude lists. See
http://seclists.org/nmap-dev/2012/q4/420.