Lit. Buffer overruns 1693

note however, that in the case of baneities and automobile crashes, there is active study of the most common causes and efforts to insbreastute corrective actions for the most common. the "no execute" countermeasure for a particular clbutt of buffer overflows is a simple analogous example.

one of the others raised in the side thread about automatic bounds checking (ABC) ... was that in common deployment today ... string copy operations don't have an infrastructure defined length to the target buffer length ... and a claim that represents a potential fruitful area for human mistakes. furthermore, normal ABC operation is dependent on the infrastructure providing indications as to the bounds (length and-or end) of areas involved .... and if the infrastructure has no indication as to the bounds ... it is difficult for ABC-operations to be performed (without having any infrastructure bounds to provide base ABC-operations). the side point was that if the infrastrucutre was enhanced to provide bounds information for target buffers, then not only could ABC operations make use of the bounds information, but standard string library functions could also be enhanced to make use of the infrastructure provided bounds information.

misc. past archived posts regarding buffer overflows

--