the extremes of bug compatibility

http://0xeb.net/?p=65

as we know, one man's bug is another man's feature. this is a pretty fun read about how far some blizzardfags went to emulate a buffer overflow and its read/write primitves which were often used in modding.

>>13
Also consider C-based exploits enable homebrew, DRM bypasses, runtime patching (aka monkey patching, for closed source binaries)and execution(jump to buffer), numerous reverse engineering schemes(C is notoriously close to Asm, making RE much simpler),game hacks/mods not approved by publishers, etc.
In general C gives a Joe Hacker more power vs large organizations, making all software pliable and "modifiable".
While the threat of malware(generally limited to poorly designed OSes/softwares) exists it counterbalanced by Freedom to Tinker.
It also ensures no programmer can half-ass his C code, unless he want to invite vulnerabilities everything(includes non-C related logic of software) has to be tested and sanitized.That why C builds better programmers, they get trough the "bootcamp of C horrors" and recognize flaws in all code they see.