News for hackers. Stuff that matters.
Re:Imposing memory security in C [video] by woodruffw on Thursday February 27, 2025 @12:22PM (#43196391)
> Not sure the data is clean enough to draw meaningful conclusions because of confounding factors.

I'm thinking of things like the Windows user- and kernel-mode font parsers; these have a pretty long and steady public history of exploitation that seems to have mostly stopped with the Rust rewrite 1-2 years ago. I don't think that's because vuln researches have stopped looking at them!

But yeah, I would like it if Google and Microsoft (among others) would put more hard data out there. I don't think of the Windows kernel teams as typically suffering from hype-driven development, so my abductive conclusion is that they have strong supporting data internally.

Edit: here's a hard data source from Google, showing that Rust has contributed to a marked decline in memory unsafety in Android[1].

[1]: https://security.googleblog.com/2022/12/memory-safe-language...

Re:Imposing memory security in C [video] by pizlonator on Thursday February 27, 2025 @12:43PM (#43196593)
That's good data, but: is the reduction in vulns because Rust is safer, or is it because vuln researchers assume it's safer and so choose to look for vulns in C/C++ code because it's what they're familiar with?

It's hard to say.