Re:Glibc getaddrinfo stack-based buffer overflow
by steveklabnik on Tuesday February 16, 2016 @01:58PM
(#11112240)
This is sort of what Cyclone tried, in a way.
[ Parent
| on HN ]
Re:Glibc getaddrinfo stack-based buffer overflow
by mikeash on Tuesday February 16, 2016 @02:06PM
(#11112287)
Cyclone looks cool, but it's a pretty significant departure from normal C. I'm wondering how far you can take safety without changing the actual language at all. Or rather, how far you can take safety without changing the language and without completely killing performance. Memory safety shouldn't be hard: track all valid regions and pointers to them and don't allow mixing stuff up. But doing it fast is tough.