Nmap Development mailing list archives

Re: symmetry in nping echo protocol


From: Toni Ruottu <toni.ruottu () iki fi>
Date: Sun, 13 Feb 2011 22:50:41 +0200

So the response comes through the side-channel, and server-side nping
can not access the actual response that is sent, because it is an ICMP
message sent automatically by the OS, or some middle box. This
invalidates my suggestion. I misunderstood the side-channel thing at
first.

On Sun, Feb 13, 2011 at 6:09 PM, Toni Ruottu <toni.ruottu () iki fi> wrote:
good day

I started exploring the world of nping echo today. It is an
interesting project, and I wonder if the service could be used as a
part for implementing future NAT traversal protocols and such. It is
similar to some techniques used in STUN and Teredo, but more general
purpose as it has not been designed for a single purpose in mind.

Would it make sense for the echo server to include information about
the message it is sending to the encrypted response packet, so one
could do some reasoning both ways by just looking at the client. I am
thinking about a new output line type RESP. After this change we would
have

SENT - the packet that was sent to server
CAPT - the packet the server received
RESP - the packet that the server sent back
RCVD - the packet that we received

The message that the server send back would contain information for
both CAPT and RESP.

 just a thought, --Toni

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/


Current thread: