mirror of
https://github.com/nmap/nmap.git
synced 2026-08-04 14:49:29 +00:00
Moved old item to the done section
This commit is contained in:
parent
61ca42638d
commit
d21024f87f
1 changed files with 6 additions and 6 deletions
|
|
@ -75,12 +75,6 @@
|
|||
line, should we use that version, or the official rDNS, if any?
|
||||
- Some more discussion on this topic on nmap-dev may be warranted.
|
||||
|
||||
* Try to reduce the size of the internal buffer in the EchoHeader class.
|
||||
Currenltly it allocates a big buffer that is able to hold the theoretical
|
||||
maximum size of a NEP message (normal use does not require so much space).
|
||||
When this is done, check if we still need to increase the stack size
|
||||
in the project properties in Visual Studio.
|
||||
|
||||
* Do some performance testing.
|
||||
Fyodor:
|
||||
<<Nping should be able to send packets quickly, at least comparable to
|
||||
|
|
@ -641,4 +635,10 @@
|
|||
- We should probably set -c 32 when --traceroute is specified,
|
||||
unless user specifies their own -c explicitly.
|
||||
|
||||
[DONE] Try to reduce the size of the internal buffer in the EchoHeader class.
|
||||
Currenltly it allocates a big buffer that is able to hold the theoretical
|
||||
maximum size of a NEP message (normal use does not require so much space).
|
||||
When this is done, check if we still need to increase the stack size
|
||||
in the project properties in Visual Studio.
|
||||
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue