Cited on HN 3 times, 2024–2025, never outright recommendedscore 0
Years with an HN recommendation, 2007–2026
HN cites it as the key account of train DRM being broken, in threads on right to repair, reverse engineering and vendor lockouts.
A 37C3 talk on how a series of Polish electric trains stopped working after servicing by an independent company. The speakers explain how train control systems work and how they reverse-engineered the software lockouts.
Oh, I know something about this. Some people that made this are part of DragonSector [1] polish hacking group that broke DRMs in trains quite recently [2]. Sadly I joined company after there were long gone. Really surprised seeing this posted here as it was pointed out, the repo is pretty old and archived. [1]: [link] [2]: [this video]
Talk on Dragon Sector hackers breaking DRM in Polish trains
The whole train DRM saga has been endlessly entertaining as someone looking in from afar, but I can only imagine the stress this must place on operators trying to keep trains maintained with this dagger dangling over their heads. I wish I could hack a train, thats a once in a lifetime opportunity and would make for an incredible "2 truth and a lie" type story Also available at [link] Previous coverage: "37C3 - Breaking "DRM" in Polish trains" [this video] "O trzech takich, co zhakowali prawdziwy pociąg – a nawet 30 pociągów" [link] Mastodon post by q3k [link]
I'm not sure this comment does justice to the situation. Poland put out a separate bid for manufacturing and servicing of their locomotives and one company won the manufacturing bid while another won the servicing bid. The servicing company was unable to get the trains into working order and after hiring hackers accused the manufactoring company of bricking the software on purpose by including geo-fences where the trains would no longer work after arriving at the servicing company's property. Perhaps the interesting part to me was Dragon Sector's (the hackers) claims that the software needs to be blessed so although they discovered problems they never changed anything because they don't have the authority to bless it and heavily imply that the fact that the manufactoring company is changing the software at will is illegal. The changes by the manufactoring company had an (undisclosed) activation sequence added to it so you didn't need to modify the software in order to get the train working so the servicing company never actually modified the software. [this video] [link]
Hackers' account of locomotive software lockouts and servicing dispute
Video list and Hacker News comment labels from HackerTube (prompted by @karpathy), released under ODC-By 1.0, built on the open-index/hacker-news archive. Hacker News data is provided by Y Combinator; comments remain the work of their authors. Video titles, channel names and thumbnails belong to their creators and are shown via YouTube. HackerTube Watch is an unofficial edition. Data export of 2026-10-31.
Plays via YouTube's privacy-enhanced embed
3 Hacker News comments
From the HN archive; up to 20 kept per video, favoring different commenters. Recommendations first.
Read more