Re:Glibc getaddrinfo stack-based buffer overflow
by steveklabnik on Tuesday February 16, 2016 @01:48PM
(#11112145)
Only portions of it do. The whole point of unsafe is that you can encapsulate it, and then go from there.
[ Parent
| on HN ]
Re:Glibc getaddrinfo stack-based buffer overflow
by autoreleasepool on Tuesday February 16, 2016 @02:00PM
(#11112249)
Definitely. The ability to encapsulate code that is less strictly checked by the compiler is what makes Rust such a compelling alternative to C. I definitely think Rust is the ideal choice for a hobby kernel from scratch in 2016.
My point is that unsafety is unavoidable. You can encapsulate unsafe Rust or wrap plain old C, it's, for all practical purposes, the same. At that level language features matter a lot less. I agree we should minimize and encapsulate loosely checked code as best we can.
Re:Glibc getaddrinfo stack-based buffer overflow
by steveklabnik on Tuesday February 16, 2016 @02:08PM
(#11112312)
Yeah, absolutely. Ultimately, the machine is not safe. Such is life.