From e04f9d24ecb9d4aa1fb9a2ffc55a800c736c5fe5 Mon Sep 17 00:00:00 2001 From: luis Date: Fri, 1 Apr 2011 14:38:18 +0000 Subject: [PATCH] Add note about how the current echo server zeroes application layer data before encapsulating packets in NEP_ECHO messages, and how in the future we may want to extend the echo protocol to allow stripped-packet transport --- todo/nping.txt | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-) diff --git a/todo/nping.txt b/todo/nping.txt index 86245dc28..ad3d14c0f 100644 --- a/todo/nping.txt +++ b/todo/nping.txt @@ -54,7 +54,7 @@ level. None of them seems to work well, though. * Consider using Nmap's proto-dependant payloads for UDP packets. According - to his tests, better results are obtained when sending UDP probes with a + to David's tests, better results are obtained when sending UDP probes with a payload specific to the protocol. * A few ideas for the Echo protocol: @@ -70,7 +70,18 @@ - RFC. Improve description of encryptionless sessions. Suggested by Toni Ruottu. - + + - Currently, the echo server zeroes any application layer data before + transmission in a NEP_ECHO message. This minimizes the impact of + errors in the server's packet matching engine or malicious attacks that + attempt to trick the server into echoing packets that do not belong to + a particular user. This works well but in the future, if one day we + create a NEPv2 specification, we may want to consider extending NEP_ECHO + packets to allow stripped-packet transport. This is, to allow echo servers + to remove application layer data before transmission, and include + additional information in the NEP_ECHO message so clients can determine + that the payload part was stripped and how long was it. + * Investigate about warning on old version of gcc like g++ 4.1.2 20080704 (Red Hat 4.1.2-48). No warnings are shown on newer version but it would be nice to get rid of them if possible. There are some of them: