News for hackers. Stuff that matters.
Re:A Sad Day for Rust by kelnos on Friday January 17, 2020 @04:45PM (#22079744)
Yes, and you're making the same mistake that you're railing against: if you're going to invoke some sort of moral imperative to do something, you have to examine the risk of what can happen if you do nothing. In the case of something like Heartbleed, yes, the consequences of silence could be quite high. But I just can't see the same argument against remaining silent for this web framework.

It's also a matter of degree and thoroughness. There's a huge difference between "I've found a specific exploitable vulnerability in this security library and here is a proof-of-concept exploit", and "after a cursory look, I see this rust code uses a lot of `unsafe` and I'm uncomfortable with that".

Re:A Sad Day for Rust by nindalf on Friday January 17, 2020 @04:59PM (#22079903)
There were specific issues found in this library. Soundness holes as a result of unsafe. And people submitted fixes. This person could literally have done nothing and it would have been ok. But they went out of their way to be terrible to everyone.
Re:A Sad Day for Rust by chachachoney on Friday January 17, 2020 @07:27PM (#22081184)
Seems like there was plenty of actual terrible to go around, and the language barrier made quite a few instances of not terrible seem terrible.