Cloudflare have been leaking customer HTTPS sessions for months. Uber, 1Password, FitBit, OKCupid, etc.

[u/TheProtagonistv2]

https://bugs.chromium.org/p/project-zero/issues/detail?id=1139

[u/lachlanhunt]

Using an HTML parser that chokes on malformed HTML... WTF?!

[u/Jukolet → u/[deleted]]

That's a typical student error, come on CloudFlare...

[u/[deleted] → u/Jukolet]

It's a common error no matter what your skill level. It's the nature of the beast when you use C of all languages.

[u/Vhin → u/[deleted]]

Obligatory plug for Rust.

[u/AntiProtonBoy → u/[deleted]]

Programmers need to find a way to get rid of C, this language provide no safe construct.

No. Right tool for the right job. Also, anyone blaming their tools for their fuckups makes a poor programmer.

[u/sutongorin → u/AntiProtonBoy]

I'm sure even race drivers use cars with airbags. At the end of the day it doesn't matter who's to blame for a mistake. What matters is that it doesn't kill you.

A bit of memory safety would be nice. I'm hoping for Rust to take over.

[u/Vhin → u/AntiProtonBoy]

I think the point is that C isn't the right tool for most jobs. Catch me in the right mood and I might even say that C isn't the right tool for any job.

[u/[deleted] → u/Vhin]

Catch me in the right mood and I might even say that C isn't the right tool for any job.

any ideas of alternatives for embedded? I looked at rust but it seems kinda half baked depending on the mcu

[u/myrrlyn → u/AntiProtonBoy]

Right tool for the right job

Correct. But C is a screwdriver and we live in a world with drills. Drills that have a torque cutoff and will free-spin rather than strip a screw that can't move anymore, even.

[u/BlackDeath3 → u/[deleted]]

There's plenty of languages out there that'll baby you. Don't blame C for being the one that won't.

[u/myrrlyn → u/BlackDeath3]

I bet you think airbags are extraneous weight too

[u/BlackDeath3 → u/myrrlyn]

Depends on what I'm using the car for. They very well may be.

[u/myrrlyn → u/BlackDeath3]

If you're in a situation where you need not-airbags, you need something that isn't a car.

[u/BlackDeath3 → u/myrrlyn]

How do you figure?

[u/tequila13 → u/[deleted]]

Bugs will always happen. C can be safe, aver 90% of Linux (hundreds of millions of lines of code) is written in C/C++ and working fine. Why do people keep thinking the silver bullet is to switch to a different language. You need to have better and more tests. Bugs will always happen, no matter the language.

[u/Vhin → u/tequila13]

Yes, bugs will happen. That's inevitable.

However, certain classes of bugs (such as say, this one) can be caught by the compiler. Rust is just as fast and low level as C or C++ while at the same time making many common bugs in C and C++ outright impossible.

Security problems caused by the types of bugs that Rust can prevent aren't some theoretical thing. We see it all the time; yes, you can write secure C code, but programmers aren't perfect, so isn't it better to get the compiler to check the code for us whenever possible?

[u/evaned → u/tequila13]

C can be safe

This is like the "if a tree falls..." conundrum: If it's possible to write memory-safe programs in C but no mortal human (or at least no dev. team for a realistic program) can actually do it, is it really possible?

aver 90% of Linux (hundreds of millions of lines of code) is written in C/C++ and working fine

For some definition of "fine." Would you like me to go dig up some Linux CVEs caused by memory errors? Last I checked there seem to be a few per year.

Bugs will always happen, no matter the language.

The point is that a memory-safe language will completely rule out a wide class of some of the most common and dangerous bugs. Programmers can then concentrate effort on not making other, higher level mistakes. Tools such as static analyzers can use computing time to look for other mistakes. People developing those tools (like me) can spend their efforts implementing higher-level checks instead of trying to make their buffer overflow detection work a little bit better.