Re:OpenSSL Security Advisory
by lmm on Tuesday May 03, 2016 @11:50AM
(#11621701)
That wouldn't help. GCC would just compile code that turns off those features, since that would help it do better on benchmarks.
[ Parent
| on HN ]
Re:OpenSSL Security Advisory
by Sanddancer on Wednesday May 04, 2016 @02:44AM
(#11626639)
To those downvoting lmm, look up C11 Annex K. There are standards for adding bounds checking and the like to C, but compiler makers don't implement them because they're "too slow." We need to demand more of our tooling makers.
Those "features" would be built into the platform. Instead of having the return stack and the parameter stack share memory space, the stacks would be kept separate by design. Instead of having malloc_chunks, the MMU would keep allocation metadata separate from the data presented to the user space. Any process overwriting an allocation would result in a segmentation fault, not on a per-page basis but on a per-allocation basis. It would be enforced by the architecture. It would not be optional. It would be by design.
Re:OpenSSL Security Advisory
by ThisIs_MyName on Tuesday May 03, 2016 @01:15PM
(#11622494)