BSD 'eliminates' buffer overflow errors/hacks
It seems that the Open BSD guys have tried to eliminate buffer overflow errors/hacks by several methods (randomising where in the memory things should sit, including procedures to detect changes in memory pointers and by separating executable and writable portions).

This should be good, and is an excellent example of how people should and could do things to prevent problems from happening, instead of fixing them after they happen.

The best part of the article? "This really wasn't part of the DARPA grant," he said. "But it happened because the DARPA grant happened, because when you throw a bunch of...guys into a room and get them drunk, this is what you get." De Raadt was careful to point out that the group paid for its own beer.