From: Michael Bevilacqua-Linn <michael.bevilacqualinn@...>
Date: 2007-09-10T05:24:03+09:00
Subject: Re: Custom Packets

------=_Part_4864_6763230.1189369438640
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Huh?

Coding in assembly isn't "hard" either, in the sense that the basic concepts
aren't all that difficult to understand.

It does, however, require a level of focus and attention to detail that is
much higher than generally needed with the higher level languages most of us
work in most of the time.  Making a small mistake in the wrong place lead to
whatever you're trying to build failing horribly in some difficult to debug
fashion...

Custom network protocols (which is, I think, what you're talking about
here?) are probably similar...  Sure it's a "just" a stream of bytes, but
they need to be *exactly* the right bytes...

MBL

On 9/9/07, Ari Brown <ari@aribrown.com> wrote:
>
> Hey all,
> So if packets are just streams of bytes sent out to a device....
>
> Why is crafting custom packets so hard? Couldn't you just formulate a
> string of the information, and then send it to the device?
>
> From the Curiously strong mint,
> Ari
> --------------------------------------------|
> If you're not living on the edge,
> then you're just wasting space.
>
>
>
>

------=_Part_4864_6763230.1189369438640--