Lit. Buffer overruns 1722
although there are machine instructions that require explicit length bounds before the instruction starts ... so there are some instruction semantics that require that both origin and destination...
remember current mac-os (and NeXT) is a derivative of mach from cmu ... a unix microkernel implementation.
in the 70s, we got to shot an email network scripting exploit ... and basically came back with the recommendation that automatic command scripting of network arrived files will need to be prevented. there has been a whole clbutt of viruses starting (at least) in the late 90s having to do with automatic scripting of network arrived files (visual basic, javascript, java, etc). some number of this clbutt of viruses tend to be application related and whether or not they support automatic scripting of network arrived files.
job. No, it doesn't. If you read these posts carefully, you'll discover that a lot of the mistakes are because people never maintained the code. They are inseparable facets but a coder who has...
note however, there are parts of the mac environment that have been susceptible to buffer overflow attacks ... and it is specifically these that the AMD hardware is a countermeasure for.
the issue with the no-execute paradigm is that the c language environments have been thick with buffer overflow vulnerability exploits ... dating back to at least the morris-internet worm. It isn't a fix for buffer overflow software bug ... using a biological analogy ... buffer overflow vulnerability is an infection vector. the no-execute paradigm is trying to keep the patient alive (as opposed to eradicating the bug).
--
Alt Folklore Computers from Newsgroups