It isn’t if it was intentional. It was intentional. Otherwise the exploit chain wouldn’t be so convoluted.

Where I work there is a hardware test, where the voltage needs to be changed on the power supply like 8 times. Currently it’s done by hand.

I gave that to a student with the description that I want that automated, let production show you how the test is done. If you have other ideas how to improve it, just do it.

This was 8 working days ago for the student. She still hasn’t started, because she wants an exact description what needs to be done. If you want me to write down how exactly everything needs to be done, I might just write it myself in python and be done with it.

Maybe because of the privilege escalation that was just found in glibc?

https://www.bleepingcomputer.com/news/security/new-linux-glibc-flaw-lets-attackers-get-root-on-major-distros/

Other languages: if a is null return b.

Rust: here is an array of strings, we are going to parse the array to numbers. If that conversion fails we handle the exception and return the minimum integer value. We then save the result in a new vector. We also print it.

I like rust, but I hate the example too. It’s needlessly complex. Should have just been a.unwrap_or(b).

Anything is more efficient without cost+ contracts, where the cost is covered + a fixed percentage profit on top.

Those kinds of deals make the cost explode somehow. Who would have thought.