27c3: Console Hacking 2010 (en)
Christiaan0082 HN recommenders · recommended in 2 months, 2019-2026
33K views · 15 years ago · talk · evergreen
The fail0verflow team (bushing, marcan, sven) present console hacking at 27C3, covering Wii, Xbox 360 and PS3 exploits. They explain how the PS3 was cracked after Sony removed Other OS.
HN recommends it as the primary source on Sony's ECDSA nonce-reuse blunder and the history of console cracking.
44:40DCEmu Reviews - 27C3 - Chaos Communication Congress 2010 - fail0verflow - FULL VIDEO
1KIND Reviews
47K views • 15 years ago
53:44Console Hacking 2016 (33c3)
media.ccc.de
166K views • 9 years ago
56:5034C3 - Console Security - Switch
media.ccc.de
135K views • 8 years ago
5:01How a Laser-Shot Disk Defeats Hackers & Pirates (Coding Secrets)
GameHut
132K views • 8 years ago
27:09Sega Saturn CD - Cracked after 20 years
debuglive
4.4M views • 10 years ago
58:44TasBlock at AGDQ 2017: TASBot
TASVideosChannel
398K views • 9 years ago
31:37How Crash Bandicoot Hacked The Original Playstation | War Stories | Ars Technica
Ars Technica
5.2M views • 6 years ago
22:21Reverse emulating the NES to give it SUPER POWERS!
suckerpinch
1.1M views • 8 years ago
1:14:5627C3: Adventures in analyzing Stuxnet (Bruce Dang from Microsoft)
basti0007
95K views • 15 years ago
12:09How I Fixed a 10 Year Old Guitar Hero Bug Without the Source Code
ExileLord
404K views • 9 years ago
6:08Super Mario World: Arbitrary Code Injection At AGDQ 2014, Performed Live
invalidation
225K views • 12 years ago
5:22:14The Complete History of the A Button Challenge
Bismuth
2.4M views • 3 years ago
2:29[TAS] Super Mario World "Arbitrary Code Execution" in 02:25.19 by Masterjun
Masterjun3
943K views • 12 years ago
53:0236C3 - A systematic evaluation of OpenBSD's mitigations
media.ccc.de
18K views • 6 years ago
39:03RustConf 2020 - Closing Keynote by Siân Griffin
Rust Programming Language
10K views • 6 years ago
11:55Super Mario World Credits Warp Explained
Frieze
638K views • 11 years ago
23:55The Fall of Minecraft's 2b2t
FitMC
7.3M views • 5 years ago
3:05Why does PUNCHING Sonic 3D trigger a Secret Level Select?
Coding Secrets
510K views • 6 years ago
45:32BlueHat Seattle 2019 || Guarding Against Physical Attacks: The Xbox One Story
Microsoft Security Response Center (MSRC)
7K views • 7 years ago
1:53:34The History of Tetris World Records
Summoning Salt
7.3M views • 2 years ago
4 comments from Hacker News
I'm a frankly rather disgusted at the comparison (or suggestion of) using an LLM to correct the record. So instead I used the 20 watt "LLM" behind my eyeballs running on snacks to reaffirm my memory as someone who was there. Going through old news articles and WayBackMachine where needed. Sadly your own blog was privated and not archived, which makes some things difficult. But news reposts from other sources were helpful! Back in Jan 2010, Digital Foundry did an excellent cover of your work on the PS3's hypervisor attack [1] Grabbing some choice quotes from that article: - "the all-important decryption keys are held entirely in the SPU and can't be read by Hotz's new Hypervisor calls" - "The other security element is the so-called root key within the CELL itself. It's the master key to everything the PS3 processes at the very lowest level, and according to publicly available IBM documentation, it is never copied into main RAM, again making its retrieval challenging. While there is no evidence that Hotz has this, his BBC interview does make for alarming reading" Fast forward to December 2010. 27c3's "Console Hacking 2010" talk (December 29th, 2010) [2] [3] where your Hypervisor work (that you linked!) is mentioned at 4:25 or so. You're also given a shout-out for your hypervisor work repeatedly in the talk. With the link you provided described at 18:25. Described as "really unreliable" and "eh whatever" due to requiring hardware modification and only granting rudimentary hyperv
If anyone is interested in the cryptography mistake that Sony made I recommend watching the Console Hacking talk at 27c3 by the fail0verflow team: ▶ this video
I believe the patent issue was by far the dominant friction for adoption in 2000s. On the NIST curve problem, well, maybe FUD, but evidently, they indeed backdoored the elliptic curve-based random number generator, so I would say some distrust is warranted. Irrespective of the curve issue, ed25519/x25519 is superior and has other nice properties like not catastrophically breaking if you can't generate a unique random "k" for ECDSA as PlayStation discovered the hard way[1]. [1]: ▶ this video
This doesn't take anything away from Sony's decision making, but removing OtherOS never really helped them "get good security". The PlayStation 3 was cracked wide open [1] without OtherOS and because people were pissed at its removal. On Playstation 3s released in the first 3.5 years of its lifespan you can get full hypervisor compromise without any hardware mods, and you can yet again run OtherOS on the latest firmware. Now with less restrictions than before. Newer PS3s (starting with CECH-25xx) have 'only' been partially compromised. They can't run OtherOS, but they can still run homebrew and piracy despite Sony taking OtherOS away. Maybe it's a bit of solace that this stuff only punished Sony. But inevitably, the lesson they learnt is "we'll never experiment with this stuff again". [1]: This video is really worth watching if you're interested in this stuff: ▶ this video