On CBS MoneyWatch: Report: Tiger to Pay Wife $60 Million
BNET Business Network:
BNET
TechRepublic
ZDNet
TalkBack 2 of 6:
Next »
« Previous
Re: Hmm...
This was my understanding, and I've had half a pint of Jack Daniel's, so bear with me and please correct me if I'm wrong.

Buffer overflows work by writing past the end of a buffer into the next instruction. This works because data is data. NX is supposed to work around this by having two types of data storage: instruction (executable), and data (non-executable). I'm not 100% on how this is going to help anything. I can make a few somewhat educated guesses, most likely wrong, but I'm sure the slashdot crowd on the way in will know much better than I do.


[oldskool]
Strongly typed languages with well written code don't have buffer over runs.

So, how does the CPU protect us from the bad code which does?
Posted by: cuervo_z   Posted on: 05/17/04 You are currently: a Guest | Members login | Terms of Use

Alert moderator to an offensive message

Subscribe to this discussion via Email or RSS

Hmm ... how does CPU detect a buffer over run?  oldskool | 05/17/04
Re: Hmm...  cuervo_z | 05/17/04
It doesn't protect buffer overflows, just payloads  bluefoxicy | 07/17/04
DRM anyone?  No_Ax_to_Grind | 05/17/04
or... PalldiumII: sneaking it under the consumers' nose?  ryusen | 05/17/04
I have this feature already- I "executed" my Windows CD  Xunil_Sierutuf | 05/18/04

What do you think?

SponsoredWhite Papers, Webcasts, and Downloads

advertisement
advertisement

Meet Doc