News for hackers. Stuff that matters.
Re:OpenSSL Security Advisory by Scea91 on Tuesday May 03, 2016 @11:39AM (#11621587)
C++ is vastly different animal than C in this case. Most of the problems with C you are implying here are non issues in modern C++.
Re:OpenSSL Security Advisory by Someone1234 on Tuesday May 03, 2016 @11:45AM (#11621654)
The key being modern C++.

A lot of C++ projects aren't written in modern C++ and out of the few that are, even then, programmers will mix in older less secure C++ because they lack experience with modern C++. So habits can actually hurt security.

Ultimately when you have a language which mixes secure and insecure practises and lets the programmer decide, as an outside observer you have to assume the worst unless shown otherwise. C++ can be written very well, but C++ can also be written no better than C, it is project by project for which is which.

Other languages don't have this issue. If you see a Rust, Go, Java, C#, etc block of code you can make certain assumptions about what classes of security issues it won't have.

Re:OpenSSL Security Advisory by oconnore on Tuesday May 03, 2016 @01:22PM (#11622569)
You're saying exactly the same thing.

"This environment can shoot me in the foot, but not if I do it right."

MISRA C with copious static analysis and a talented QA team is safe, too!

Re:OpenSSL Security Advisory by pcwalton on Tuesday May 03, 2016 @03:44PM (#11623610)
> Most of the problems with C you are implying here are non issues in modern C++.

No, they aren't. Use after free is just as exploitable and is a severe concern in C++. In fact, it's worse in C++ than in C, due to the ubiquity of vtables.

Re:OpenSSL Security Advisory by steveklabnik on Tuesday May 03, 2016 @01:36PM (#11622673)
Web browsers use modern C++ and still have security issues. It's a step forward, but not a panacea.
Re:OpenSSL Security Advisory by abiox on Tuesday May 03, 2016 @03:48PM (#11623639)
to what extent? i imagine the codebases are quite...mature. and gigantic.
Re:OpenSSL Security Advisory by pcwalton on Tuesday May 03, 2016 @03:53PM (#11623668)
Everywhere. We have been using smart pointers for a long time.

Modern C++ doesn't add any memory safety protection beyond that which was already available with custom smart pointers in earlier versions of C++. In fact, I think modern C++ is less safe than earlier versions, due to new classes of potential bugs like use-after-move and the ease with which closed-over variable references in lambdas can become dangling.