It's a wild read: https://zaufanatrzeciastrona.pl/post/o-trzech-takich-co-zhak...
It appears to be malicious code included by the manufacturer to prevent third party repair that at one point included geolocation for triggering. Given that the train operator had to reduce train schedules for this which impacted service and income, it might end up as evidence in a lawsuit against the manufacturer at some point.
There's a lot of indirection and zero strings in the resulting code, meaning it's very difficult to actually find whatever logic you're looking for. But once you see it, it is obvious and seems like it was built like any other logic.
Must be very satisfying to find something like this.
I guess this is going to provide plenty of billable hours for lawyers at this point...
>Until a few years ago, rolling stock manufacturers such as Newag from Nowy Sącz and PESA from Bydgoszcz were able to dominate the maintenance market. It was mainly them who entered tenders for compulsory maintenance of their vehicles, because other companies knew they were at a disadvantage. At the time, the dominant narrative of the manufacturers was that the "Maintenance System Documentation," a kind of manual for a given vehicle, was the manufacturer's secret, its intellectual property, and under no circumstances could this be passed on to other service companies. This led to a situation in which railroad companies across the country were forced to use the manufacturer's expensive service. And the latter, having a monopoly on repairing its trains, dictated outlandish prices, even tens of percent higher than another company would have given, the rail safety expert points out.
>Our source adds that later, thanks to the European Union Agency for Railways, the interpretation of regulations changed, allowing other companies access to service trains. This led to the opening of the market to other companies in the industry.
[1] - https://wiadomosci.onet.pl/kraj/awarie-pociagow-newagu-haker...
https://zaufanatrzeciastrona-pl.translate.goog/post/o-trzech...
> if the month is greater than or equal to 11 and
> if the year is greater than or equal to 2021
> then report a compressor failure.
> [...] It was probably the software author's inability to construct IFs that made it necessary to wait until November 21, 2022 for the planned failure.
Oops!
Economic theory(?) would suggest that if they don't do this, their competition eats their lunch and drives them out of business.
heck, Volkswagen did something much shadier to get their vehicle's emissions to comply
for those of you who like me can't quite understand literally anything otherwise
They were contacted by workshop which was doing maintenance of those trains and had no idea why they stopped working