4 ms·

Since nobody else has said it yet, it looks like most, if not all, of these vulnerabilities would not have happened were the libraries written in Rust.

by eridius 10y ago

coroutines 10y ago
Oh behave. ;p
sievebrain 10y ago
Or any memory safe language. Heck, you could implement image decoding by doing an RPC to a sandbox with a shared memory segment that decoded the image to a device bitmap using Java or C# or JavaScript or pretty much anything. Java specifically doesn't have this issue because its image decoders (except for JPG) are written in Java itself. So whilst for the types of library that Apple OS' use, rewrites in Rust would avoid any odd IPC issues and be the most obvious drop-in replacement, you would pay the cost of rewriting the libraries as I guess there are no mature Collada or OpenEXR libraries in Rust. I do see a TIFF library though it says it doesn't support interlaced images.
pjmlp 10y ago
Any sane systems programming language for that matter, but those weren't given for free.
JustSomeNobody 10y ago
I cannot wait until the first nasty exploit due to a Rust vulnerability. I just can't.
- amelius 10y ago
  Those vulnerabilities will most likely be of the form "developer got annoyed by Rust's overly complicated typesystem, and took some shortcuts".
- TillE 10y ago
  Indeed. There's a whole universe of logic bugs that lead to serious exploits. Memory safety is nice, but I wish Rust evangelists would 1) stop acting like it's a panacea, and 2) acknowledge that Rust isn't really fully baked yet. I have various complaints about the language and standard library, but the real show-stopper is this: https://github.com/rust-lang/libc/issues/290 https://github.com/rust-lang/libc/issues/290
- tdb7893 10y ago
  Yeah, they are pretty smug about it. The problem is that nothing short of perfect developers will completely stop errors but seeing how we see major memory safety exploits in C at least a few times a year for the past couple decades it might be time to start considering come sort of solution, whether it is Rust or otherwise.
coldcode 10y ago
There is no software or hardware with provable perfect security; given enough time everything has a vulnerability. Even black holes leak information.
- johncolanduoni 10y ago
  So what does that have to do with the claim that (safe) Rust would help prevent a large class of vulnerabilities encountered in the wild? It's like saying you shouldn't bother with windows that provide better thermal insulation in your house because "some heat will always get through". Some people do wrongly act like Rust will solve all security issues forever, but the OP did not.

Since nobody else has said it yet, it looks like most, if not all, of these vulnerabilities would not have happened were the libraries written in Rust.

by eridius 10y ago

Since nobody else has said it yet, it looks like most, if not all, of these vulnerabilities would not have happened were the libraries written in Rust.

coroutines 10y ago

Oh behave. ;p

sievebrain 10y ago

Or any memory safe language. Heck, you could implement image decoding by doing an RPC to a sandbox with a shared memory segment that decoded the image to a device bitmap using Java or C# or JavaScript or pretty much anything. Java specifically doesn't have this issue because its image decoders (except for JPG) are written in Java itself. So whilst for the types of library that Apple OS' use, rewrites in Rust would avoid any odd IPC issues and be the most obvious drop-in replacement, you would pay the cost of rewriting the libraries as I guess there are no mature Collada or OpenEXR libraries in Rust. I do see a TIFF library though it says it doesn't support interlaced images.

pjmlp 10y ago

Any sane systems programming language for that matter, but those weren't given for free.

JustSomeNobody 10y ago

I cannot wait until the first nasty exploit due to a Rust vulnerability. I just can't.

amelius 10y ago
Those vulnerabilities will most likely be of the form "developer got annoyed by Rust's overly complicated typesystem, and took some shortcuts".
TillE 10y ago
Indeed. There's a whole universe of logic bugs that lead to serious exploits. Memory safety is nice, but I wish Rust evangelists would 1) stop acting like it's a panacea, and 2) acknowledge that Rust isn't really fully baked yet. I have various complaints about the language and standard library, but the real show-stopper is this: https://github.com/rust-lang/libc/issues/290 https://github.com/rust-lang/libc/issues/290
tdb7893 10y ago
Yeah, they are pretty smug about it. The problem is that nothing short of perfect developers will completely stop errors but seeing how we see major memory safety exploits in C at least a few times a year for the past couple decades it might be time to start considering come sort of solution, whether it is Rust or otherwise.

coldcode 10y ago

There is no software or hardware with provable perfect security; given enough time everything has a vulnerability. Even black holes leak information.

johncolanduoni 10y ago
So what does that have to do with the claim that (safe) Rust would help prevent a large class of vulnerabilities encountered in the wild? It's like saying you shouldn't bother with windows that provide better thermal insulation in your house because "some heat will always get through". Some people do wrongly act like Rust will solve all security issues forever, but the OP did not.