- cross-posted to:
- right2repair@discuss.tchncs.de
- technology@lemmy.world
- cross-posted to:
- right2repair@discuss.tchncs.de
- technology@lemmy.world
Follow up to https://kbin.social/m/technology@lemmy.ml/t/700738
cross-posted from: https://derp.foo/post/544012
There is a discussion on Hacker News, but feel free to comment here as well.
Wow, so many good parts in this…
Side note: I do not do any coding professionally, just self taught stuff to impressive my business coworkers - but this was really well explained.
My favorites: Default username and password for accessing the debugger on the trains computer (that apparently can’t be changed)
Hard coded geofenced coordinates that would disable a train if it was being serviced at a competitors location
Absolute favorite: the incorrectly programmed date lock that would only disable the train November & December on the 21st-30th
Hopefully the company is reprimanded for this - here in the US it would probably be a slap on the wrist and nothing else.
This would be quite a bit more than a slap on the wrist in the US, the City of New York does all its own maintenance on all its buses, railroad and subway trains.
Manufacturer interference would result in some of the most aggressive city lawyers grinding the manufacturer’s headquarters into dust, legislatively.
I can’t believe it’d be different at any other jurisdiction within the US.
Hmm, that’s good / reassuring - hopefully we don’t have to find out!
Indeed. Luckily at least some people in power still care about quality for their citizens. Some places may not be able to afford the lawyers in spite of wanting to do the right thing, so I’m not sure what happens then.
The dice have just started rolling. Shit is possibly going to hit the fan real hard for Newag next year.
CC BY-NC-SA 4.0
From the sound of them, it sounds like the polish government will take it seriously, and it can be that its going to go be an international thing too…
deleted by creator