News for hackers. Stuff that matters.

A comment on Chromium project finds that 70% of security defects are memory safety problems. Parent comment

Re:Chromium project finds that 70% of security defects are m... by ansible on Sunday May 24, 2020 @11:19AM (#23292095)
> Rust does not compile if you don't use the techniques you described?

Yes, exactly.

https://kkimdev.github.io/posts/2019/04/22/Rust-Compile-Time...

Of course, you can bypass this by using 'unsafe' code, where you are explicitly telling the compiler that you have manually verified Rust's safety guarantees.

This is why a significant portion of Rust's community gets agitated with (possibly unnecessary) use of 'unsafe' in popular libraries.

[ Parent | on HN ]
Re:Chromium project finds that 70% of security defects are m... by fetbaffe on Sunday May 24, 2020 @11:50AM (#23292348)
Then I stand corrected and applaud the creators of Rust for haven taken these measures for writing thread safe code, because it is supereasy to get threading wrong, even for the most experienced developer.
[ Parent | on HN ]
Re:Chromium project finds that 70% of security defects are m... by littlestymaar on Sunday May 24, 2020 @01:17PM (#23292971)
Interestingly enough, this was the raison d'être of the Rust project at the beginning, while zero-cost abstraction and memory-safety without GC (and the borrow-checker) weren't part if the initial goal. When Rust was first released as a research project it had green threads and a GC (interestingly close to Go actually), but it was already designed with data-race freedom in mind.
[ Parent | on HN ]
Re:Chromium project finds that 70% of security defects are m... by thePunisher on Sunday May 24, 2020 @12:56PM (#23292812)
Both Java and C# are designed for memory-safety but not thread-safety; Rust is.

Considering many of the software problems we face have some connection to thread-safety, Rust is the way to go.

[ Parent | on HN ]
Re:Chromium project finds that 70% of security defects are m... by pjmlp on Wednesday May 27, 2020 @03:50AM (#23320509)
I would consider that the way to go is multi-processes instead, and secure every critical module on their own OS sandbox.

Threading seemed a good idea that went wrong.

[ Parent | on HN ]