8 ms·
> Yes, it does. Where is this modern C++ culture that has resulted in large-scale codebases free of memory safety vulnerabilities? I've never seen even one, m
by pcwalton 10y ago
> Yes, it does.
Where is this modern C++ culture that has resulted in large-scale codebases free of memory safety vulnerabilities? I've never seen even one, much less a "widespread culture".
> The majority of C++ programmers make use of:
None of this, empirically, results in safe code.
> Most of the unsafe C++ code is written by the "C with C++" sub-community that are mostly C refugees forced to use a C++ compiler.
I haven't seen any evidence for this. A lot of vulnerabilities are found in modern C++11.
> Also while the C++ community is pushing for safety with activities like the C++ Core Guidelines and reducing the amount of UB in the standard, the C standard community doesn't care at all.
I don't see any way that the C++ Core Guidelines are going to be able to succeed in creating a usable language that is memory-safe. Robert O'Callahan and I have elaborated why in other posts.
- pjmlp 10y ago> Where is this modern C++ culture that has resulted in large-scale codebases free of memory safety vulnerabilities? In any large scale C++ conference like CppCon. In tooling from Microsoft and Apple. > I haven't seen any evidence for this. A lot of vulnerabilities are found in modern C++11. Using C++11 idioms, or C with classes? > I don't see any way that the C++ Core Guidelines are going to be able to succeed in creating a usable language that is memory-safe. Robert O'Callahan and I have elaborated why in other posts. Rust will become a sound alternative to C++ when: - Libraries stop using nightly - Rust developers can call OS APIs like COM on Windows without gymnastics. I mean with the same ease that Delphi, C++ Builder and Visual C++ integrate with COM. - Rust developers can call OS X and iOS APIs with the same ease than Swift and Objective-C - Has IDE support that can match what QtCreator, Clion, XCode, Visual Studio, C++ Builder, Keil MDK, ... I really would like to see Rust one day supersede C++, but in what concerns C family of the languages, C++ is the safest option we currently have. I have been part of the C++ community since the early days as Turbo Pascal and strong type refugee, and have followed how hard it has been for a language that is almost copy-paste compatible with C to earn the position it holds in the industry. So until Rust gets some OS SDK love, bashing C++ community efforts to improve security won't get many adopters. I keep on playing with Rust, but I get to write production code it still is JVM, .NET languages, Swift or C++.
- pcwalton 10y ago> In any large scale C++ conference like CppCon. > In tooling from Microsoft and Apple. Microsoft and Apple regularly ship memory safety vulnerabilities in their codebases that are written in modern C++. Their browser engines, for example. > Using C++11 idioms, or C with classes? Using C++11 idioms. C++11 doesn't actually do anything to mitigate use after free, for example. In fact, I think there's a reasonable argument to be made that C++11 is less safe than C++03 in terms of use after free, because of features like move semantics and lambdas. And I'm not intending to argue "use Rust" here. There are plenty of other memory safe languages out there. I'm simply arguing that C++ is not memory safe, and it cannot be while preserving any semblance of backwards compatibility. The specific technical reasons for this have been elaborated in posts that I've sure you've seen. I'd like to see proponents of the idea that modern C++ is memory safe actually try to rebut those.
- jguegant 10y agoWhen pcwalton appears in a C++ thread, we are already past the rustwin point.
- pjmlp 10y agoThe issue is not that C++ is 100% memory safe language, it is not. Personally I would rather be using Ada or Modula-3 for the few use cases I still use C++. However in the context of security minded developers that can only choose between C, Objective-C, C++ and nothing else, C++ is the only one providing the features to write safer code. Of course if not all team members play ball it doesn't work, but it is better than not having an option at all.
- SamReidHughes 10y ago> Robert O'Callahan and I have elaborated why in other posts. One point of note is that O'Callahan's "Vapourware" post points out a problem that's solvable, it isn't some big blocker the way he claims it is. Your comment 162 days ago describes the real problem, or at least one of them. Edit, because fuck: > Where is this modern C++ culture that has resulted in large-scale codebases free of memory safety vulnerabilities? I've never seen even one, much less a "widespread culture". The rest of your post shifts the question from "is there a culture of secure, maintainable, and understandable software" to "Is C++ software free of memory flaws." Are these concepts not distinct to you? Why even bother replying, if you're going to drag the discussion into some corner like that?
- pcwalton 10y ago> One point of note is that O'Callahan's "Vapourware" post points out a problem that's solvable, it isn't some big blocker the way he claims it is. No, it is a big blocker. In fact, it's the same as the problem I pointed out, just with global variables instead of shared ptr. Aliasable mutable data is the fundamental unsolvable problem; whether it arises through global variables or shared ptr is just a detail. > The rest of your post shifts the question from "is there a culture of secure, maintainable, and understandable software" to "Is C++ software free of memory flaws." Are these concepts not distinct to you? Software that has memory flaws that enable remote code execution is not secure.
- SamReidHughes 10y ago> No, it is a big blocker. In fact, it's the same as the problem I pointed out, just with global variables instead of shared ptr. Imagine refactoring a program to not use globals but instead pass them up by const or mutable reference to where they're used. The checker can do the same imagining with an effect system. > Software that has memory flaws that enable remote code execution is not secure. Words have meaning.
- pcwalton 10y ago> Imagine refactoring a program to not use globals but instead pass them up by const or mutable reference to where they're used. The checker can do the same imagining with an effect system. Not at all. This requires higher order control flow analysis, which is pretty much guaranteed to fall down in all sorts of cases.