News for hackers. Stuff that matters.
Re:OpenSSL Security Advisory by steveklabnik on Thursday September 22, 2016 @08:11PM (#12561403)
What essential safety features are removed? The only thing I can think of this referring to is assertions, and we do the opposite: assert stays in all builds, debug_assert is only in debug builds.
Re:OpenSSL Security Advisory by bjourne on Thursday September 22, 2016 @08:17PM (#12561425)
Integer overflow checking, for example.
Re:OpenSSL Security Advisory by wbl on Thursday September 22, 2016 @08:41PM (#12561521)
Integer overflow cannot result in memory safety violations in Rust.
Re:OpenSSL Security Advisory by ben_bai on Friday September 23, 2016 @06:54AM (#12563613)
But it can overflow, which will result in a different value that the programmer might expect, which can give an attacker a nice "information leak" or worse. This could be a security bug!
Re:OpenSSL Security Advisory by gajjanag on Friday September 23, 2016 @08:54AM (#12564168)
Exactly. Memory safety is a very nice property, but is not complete by itself. This primary emphasis on memory safety was part of a critique of Rust by Andrei Alexandrescu: https://www.quora.com/Which-language-has-the-brightest-futur....

And even wrt memory, Rust (with the standard library) is not free of its own warts, see the OOM situation. See e.g https://news.ycombinator.com/item?id=10545877 for a discussion on this.

Just to be clear: I generally like the ideas of Rust. I just dislike its presentation by some as a magic solution to all kinds of concerns.