SQLite is written in ANSI C. What's your point?
https://www.cvedetails.com/vulnerability-list/vendor_id-9237...
This is my point.
This isn't even an argument here. How is he/she wrong?
It's true that the majority of C/C++ programs are riddled with memory corruption vulnerabilities. Just look at the countless CVE's of WebKit, Linux, Chrome, V8, VMWare and the list forever goes on.
There is a case for Rust to reduce or possibly eliminate these age old vulnerabilities which C/C++ find it hard to do.
You are free to change my mind. :)
Here's your hard slap in your face.
https://medium.com/@shnatsel/how-rusts-standard-library-was-...
Not really. I said 'reduce or possibly eliminate'. I already entertained the fact that even Rust has bugs. But I can't see how one example of a documented Rust vulnerability which even requires a tricky exploit chain in practice, would change my mind given the tens of thousands of memory corruption CVEs in C/C++ software. The effectiveness of Rust's claims to 'reduce' these cases of memory corruption vulnerabilities have been proven over the years.
Rust is no doubt already being tested with confidence in production by many companies for years, making it possible to compliment or replace C/C++ based programs. You too are more than welcome to change my mind. :)
Just wanted to let you know that your comment feels very misleading because you present the large number of bugs in say web browsers and contrast it with no Rust bugs in web browsers because nobody uses a Rust browser(I know Firefox has some parts in Rust but those parts are new so you can't compare it with years old code that had time to accumulate bugs and people to find them)
Applies to any memory safe programming language, not only Rust.
It won't be that easy.
Or the ones given by Google and Microsoft at Linux Kernel Security Summit 2018 and 2019.
But in OpenBSD even plan9port compiled software is done with Retguard:
>nm $HOME/Docs/c/p9p/9.aecho | grep retpo
00003150 t __llvm_retpoline_r11
https://undeadly.org/cgi?action=article&sid=20170819230157
It makes using acid(1) in OpenBSD a bit more difficult, but I almost always omit that.
Yes, it is great that OpenBSD values security over performance, but as the talk shows, not every security feature is as secure in practice as OpenBSD sells it.
Neither of them are magical.
All of them don't suffer from memory corruption, UB and use-after-free like C does.
When we security minded people talk about secure languages, we have a panoply to chose from, Swift, D, OCaml, Java, .NET, ATS, Ada, Go, Nim, Zig, Crystal and many more, yet you always think that we speak only about Rust.
This tribal way of thinking makes no sense at all. I qualify as a C and C++ developer and I'm very excited with Rust. The only baby there is is the software project we are working on.
Meanwhile I, and others have been replacing C and C++ written applications by safer stacks long before Rust was born.
And on mobile OSes, the alternative languagea that are being pushed are not Rust.
Yet the replies are always as if we are only talking about Rust as alternative.
anthk:~>syspatch -l | wc -l
15
Who cares about your toy language backed from Mozilla. Do you think the Go runtime from Docker is bug free?https://www.cvedetails.com/vulnerability-list/vendor_id-1418...
We are counting memory corruption and UB bugs here.
https://www.infoq.com/news/2019/11/microsoft-exploring-rust-...
70% of microsoft errors would be gone in future if they start using what you demean as "toy" language.
https://www.zdnet.com/article/microsoft-70-percent-of-all-se...
As a user, I don't care whether the tool is in Go, C++, Rust, or whatever else. If Docker was written in C (or Rust, or whatever else), it would have zero effect on my usage of Docker.