4 ms·
The fact this was broken by stealing a developer's SDK is disappointing. Real hackers would have disassembled the machine to reverse engineer it, rather than
by londons_explore 8y ago
The fact this was broken by stealing a developer's SDK is disappointing. Real hackers would have disassembled the machine to reverse engineer it, rather than using black market/social engineering tricks.
- robin_reala 8y agoNo true Scotsman in full play here.
- CapacitorSet 8y agoI feel like "gatekeeping" is a more appropriate term, but yeah.
- SmellyGeekBoy 8y agoIn that case, I think you'd be genuinely surprised to discover just how many things have been hacked in this way over the years.
- wolfgke 8y ago> The fact this was broken by stealing a developer's SDK is disappointing. Real hackers would have disassembled the machine to reverse engineer it, rather than using black market/social engineering tricks. You cannot assume that an attacker will have an "honor code" or that you can keep information secret from an attacker. Because of the latter one, there exists Kerckhoff's principle > https://en.wikipedia.org/w/index.php?title=Kerckhoffs%27s_principle&oldid=871573989 https://en.wikipedia.org/w/index.php?title=Kerckhoffs%27s_pr... which on a high level states that security by obscurity will in the long run become broken (and as a corollary DRM does not work).
- mrfredward 8y agoWell, I found it disappointing just from a story standpoint. I certainly wanted to read a story about clever technical hack...about someone sniffing a memory bus and writing a program to align the dump to get a valid program, or finding a complex pattern by analyzing the scrambling by hand. I suppose it's a good reminder that in the real world, the easiest way in is often through a gullible or untrustworthy employee.
- croo 8y agoExcuse me, but real hackers use butterflies. [1] 1. https://xkcd.com/378/ https://xkcd.com/378/
- wtetzner 8y agoNo, real programmers use emacs: https://emacsredux.com/blog/2013/04/03/easter-eggs/#butterfly-mode https://emacsredux.com/blog/2013/04/03/easter-eggs/#butterfl...
- cdmckay 8y agoI think if getting the SDK was enough to crack the copy protection, it would’ve happened eventually. The key seemed to be the descrambler. Why on earth did they scramble the executable in a deterministic way?
- caf 8y agoWhy on earth did they scramble the executable in a deterministic way? Because they wanted official developers to be able to create MIL-CDs that would load. They just didn't want anyone else being able to do that.
- cdmckay 8y agoJust seems like inevitably people would figure it out.
- rincebrain 8y agoDunno, you could try asking Sony, who helpfully used the same random input for every PS3 ECDSA signature, thereby leaking enough information to let people recover their private key. https://en.wikipedia.org/wiki/PlayStation_3_homebrew#Private_key_compromised https://en.wikipedia.org/wiki/PlayStation_3_homebrew#Private... (I would _suspect_ that internally, they deliberately made this choice, so that the same inputs would produce the same output, because someone important thought that was valuable and either didn't know or thought it wasn't risky enough to possibly leak key information by doing this. But I have no special knowledge, just a suspicion that people who pick elliptic curve crypto would be aware of the leaks involved in reusing IVs.)
- astura 8y agoHackers have always (and will continue to always) get more accomplished with social tricks than with technical tricks.