There are update logs of the train software. Because of them it is known that workers of the company literally snuck into waiting trains and updated the software without the owners knowing. So really, but far from that.
This is a reason why it was detected a year later - the train service was delayed and it spent late November and whole December in service. So the "expiration" intended for 2021 only manifested in 2022.
Very charitable. The "expiry date" was set to the next servicing date and there was no way for competition to fix this hardcoded date and this was not documented in the official documents. Clearly a way to force buyers to use the "official" service.
It is also investigated by the Agency of Internal Security and I really doubt they don't have huge problems out of this. This is taken extremely seriously internally.
There's a ton of evidence to prove what happened and they have no chance to somehow wiggle out of this. They're trying... by saying they were hacked. Yeah, the hackers somehow flashed firmware of trains services by competition, to brick the trains. GPS coordinates of competition rail segments were literally hardcoded.
You already face the same threat then. Many, if not most, nontrivial programs have at least one way to escalate to arbitrary code execution from config. For example sway has exec, basically any useful editor has "on save actions", etc. No need for a Turing complete language when you can just shell out.
Can you link to some study that confirms it? This sounds far too simplistic to be true, especially for something as complex and unpredictable as the economy.
Saying it's an urban legend implies it's false, but that's a bit nitpicky IMO. Most people can read most such "scrambled" sentences without a lot of effort, so that part is certainly true (and non-obvious). The original - fact checked in your sources - made don't strong assumptions like "Cambridge researchers", "can be a total mess (...) read without a problem" etc. But overall I still think that's a neat fact.
As someone who watched all the "original" marvel movies, up to a infinity war I think, I don't think anyone expected any depth from them . I wanted to watch a classical sorry full of non-subverted tropes about a hero fighting an adversary, going through a classical hero journey, and eventually prevailing (possibly sacrificing something in a process). This is a tale as old as time and I don't think there's anything wrong with it.
Of course marvel movies are devoid of any greater meaning and don't really prompt the viewer to think about anything deeper, but for me it's a feature, not a bug - when I want to think I open a technical book or start a side project.
As a pedestrian and car hater I don't mind that too much. Pedestrians always have priority on the walk signal, and there is a special separate light to allow/disallow cars to turn. In practice they are used where it's safe to implement.
But I may be wrong - statistics seem to agree with you.
I don't want to halt AI training, I want corporations to fuck off from using my (A)GPL code to train their proprietary models which they then sell to people writing more proprietary code. I would be ok if the derived code is properly GPL licenced too.
I suspect many people feel in a similar way too (for example, artists whose art is used to train image generators without compensation).
Just a side note, but it's hard to take you seriously when you resort to such childish name calling. I think your chance of convicting traders (me included) would be much higher if you used some technical arguments instead.
Can you share some examples of the outdated information and the lack of understanding by the authors, so we may all learn? From a quick skim I noticed the article mentions CopperheadOS, even though it was renamed to GrapheneOS in 2019, so I'm inclined to believe there are more outdated pieces of information. But again, highlighting the misleading fragments would be an even more valuable comment.
>The idea is that the secret key material is never compromised as it is assumed in all security cases.
That's not true, we have (perfect) forward secrecy, backwards secrecy and key rotation mechanisms because we often care what happened after the key is inevitably compromised. In this case the problem makes it hard to "rotate" the keys in a meaningful way, but I'm yet to see a proof it's impossible.