From c1057bcadd257028d966b64498aa7e92cdcb68a6 Mon Sep 17 00:00:00 2001 From: luis Date: Wed, 30 Jun 2010 16:00:11 +0000 Subject: [PATCH] Moved a few items to the DONE section and fixed a few minor style and formatting issues --- todo/nping.txt | 38 +++++++++++++++++++++----------------- 1 file changed, 21 insertions(+), 17 deletions(-) diff --git a/todo/nping.txt b/todo/nping.txt index 6b9bfa30d..df5ff5896 100644 --- a/todo/nping.txt +++ b/todo/nping.txt @@ -51,28 +51,17 @@ * [EM] Some things to keep in mind for the implementation and to update our design docs accordingly: o multi-client support - o delaying RECV message printing so the CAPT messages are shown in - order. - o send NEP_QUIT only if necessary, just close connection if possible - o Implement different "modes" for the server: complete access, one-time-access, and restricted + o delaying RECV message printing so the CAPT messages are shown in order. + o send NEP_QUIT only if necessary, just close connection if possible. + o Implement different "modes" for the server: complete access, + one-time-access, and restricted. o [EM] Things to decide on: - o Make a mockup of the desired standard output in a regular echo mode - execution, like nping -c 2 --tcp --flags SYN -p 80 scanme.nmap.org - (let's assume there are some differences found, like a NAT is in - place) - o A key aspect of this task is determining what diffs are going - to look like. o Decide on packet specifiers that can be passed to the server so it can recognize packets sent by the client even if a number of headers have changed and pass them back. (see Fyodor/Luis IM discussion logs from 6/28/10). -* [EM] Pick a default port number - -* [EM] Update EchoProtoRFC.txt and any of the other design files as - appropriate and send to nmap-dev for comments - * [EM] Begin coding the echo mode system * Fix Windows rtt values. Right now Nsock does not seem to be giving @@ -251,8 +240,9 @@ o [EM] Things to decide on: * Investigate on nping's version if devname2ipaddr. Think about side effects on using that in Nmap. -* After merging nmap-dedup, change send_frag_ip_packet() to take "u32 mtu" - and fix the printf below to use "%u" instead of "%i". +* Consider adding multi-packet support. + +* Consider adding RFC-style output for send/recv packets. /***************************************************************************** * Things that have been solved already * @@ -536,3 +526,17 @@ o [EM] Things to decide on: [DONE] Make sure randomnly generated checksums are in fact invalid and don't match the correct checksum. There is a 1/65535 chance of this happening. + +[DONE] After merging nmap-dedup, change send_frag_ip_packet() to take "u32 mtu" + and fix the printf below to use "%u" instead of "%i". + +[DONE] [EM] Update EchoProtoRFC.txt and any of the other design files as + appropriate and send to nmap-dev for comments + +[DONE] [EM] Pick a default port number + +[DONE] [EM] Make a mockup of the desired standard output in a regular echo mode + execution, like nping -c 2 --tcp --flags SYN -p 80 scanme.nmap.org (let's + assume there are some differences found, like a NAT is in place) + o A key aspect of this task is determining what diffs are going + to look like.