News for hackers. Stuff that matters.
Re:Heartbleed in Rust by baq on Monday February 02, 2015 @03:18PM (#8986654)
Rust can't solve all memory safety issues. Rust tries very hard to guarantee that safe code (i.e. not unsafe{}) will be memory safe and free of some race conditions. The hard part is making this possible - turns out you need unsafe in the core to be able to write safe implementations of those features in the general case. Attack surface is greatly lessened, but it's still there.
Re:Heartbleed in Rust by RaleyField on Monday February 02, 2015 @07:15PM (#8988062)
Other GC'd languages come with runtimes written in C/C++ and often these libraries are the source of vulnerabilities. Rust is no different, if you grep your source code and find no unsafe blocks then you are back to where you were in GC land.
Re:Heartbleed in Rust by heinrich5991 on Monday February 02, 2015 @05:05PM (#8987334)
The difference is that in Rust not the whole source code but rather only the `unsafe` blocks and what they touch need to be verified for memory-safety.
Re:Heartbleed in Rust by SamReidHughes on Monday February 02, 2015 @09:28PM (#8988536)
And often that involves verifying code outside of the blocks that are literally marked unsafe. It's all of the code sitting behind some safe abstraction boundary that needs to be verified.