It's hard to appreciate how good Rustls is at avoiding UaF since UaF avoidance is taken for granted in idiomatic Rust code. Tiny things like `#[must_use]` are small but help avoid big failures. Our friends doing concurrency & malloc/free in C are still struggling w/ the basics.
-
-
Replying to @BRIAN_____
Trying to write C/C++ after writing Rust feels ridiculous. Why should I have to keep track of things that the compiler can do for me, especially when the consequences are exploitable security bugs?
1 reply 1 retweet 9 likes -
Replying to @TedMielczarek
I agree. Though to be care, In C++ one rarely has to keep track of things manually, in modern codebases. Our experience maintaining a gigantic performance-sensitive legacy app that predates even the first ISO C++ (IIRC) biases us too much against C++.
3 replies 0 retweets 3 likes -
Replying to @BRIAN_____ @TedMielczarek
For me the biggest annoyance is that Rust doesn’t have a wonderful solution for the most pernicious UAF in browsers: unexpected reentrancy from DOM into malicious JS. I don’t know that there *is* a good solution, really…
5 replies 0 retweets 7 likes -
The fundamental problem is seamless interoperability between the ownership world (C, C++, Rust…) and the shared-everything world (DOM, JS, COM…). Hard problem, and I haven’t seen a safe, usable, and ergonomic solution yet.
1 reply 0 retweets 4 likes -
The Gecko script blockers plus static analysis seems helpful?
1 reply 0 retweets 0 likes
Helpful, yes, but sound? It’s 2018—we shouldn’t be settling for unsound solutions anymore.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.