Re: Status Report #3 of 17

[Brandon Enright <bmenrigh () ucsd edu>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 11 May 2009 22:30:38 +0000
Brandon Enright <bmenrigh () ucsd edu> wrote:

> On Mon, 11 May 2009 23:56:08 +0200
> "Luis M." <luis.mgarc () gmail com> wrote:
>
> > * Think about the Nping "echo server" features and design.
>
> > * Request feedback about the echo server on the list. (Keep Brandon
> > Enright updated on this since he's the author of the idea)
>
>
> I'm working on mocking up some
> ideas and better defining the scope of what I think is reasonable and
> useful to support.

Luis,

Attached are the beginnings of a mockup on how I see the echo server
working.  Obviously this doesn't cover the technical details like how
would the BPF filter be generated, etc.  It at least illustrates the
general usage I see for the server and in the mockup for the advanced
client, some of the analysis that can be done to see what has changed
in a packet.

I suppose we should keep most of the planning on-list but if you want
to hit me up with specifics on a higher-bandwidth channel you can reach
me via AIM at "bmenrigh" or XMPP via "bmenright () chat ucsd edu".

I look forward to hearing peoples thoughts on these mockups.

Brandon

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)

iEYEARECAAYFAkoItqQACgkQqaGPzAsl94L9fgCfUdsUseiZsvPAs/SzyvJ7QGgw
AF8AnjslcCjjOi+TTzXCwk8882DKh0av
=5HBw
-----END PGP SIGNATURE-----

Attachment: advanced_nping_client.txt
Description:

Attachment: basic_nping.txt
Description:

Attachment: basic_nping_client.txt
Description:

Attachment: basic_nping_server.txt
Description:

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