Skip to content
HHackerTube.videoSurprise me

DCEmu Reviews - 27C3 - Chaos Communication Congress 2010 - fail0verflow - FULL VIDEO

DCEmu Reviews - 27C3 - Chaos Communication Congress 2010 - fail0verflow - FULL VIDEO on HackerTube: recommended by 1 Hacker News commenter across 1 month, 2011–2015.

1KIND Reviews

talk · advanced · evergreen

Open on YouTube

The fail0verflow 27C3 talk on breaking PS3 security, covering how Sony's implementation failed, including its ECDSA mistakes.

Why Hacker News recommends it

Recommended as a fun, detailed account of how the PS3's security was broken.

people recommended it
1
separate months
1
strong recommendations
0
discussed on HN
2011–2015
“talk[1] at 27C3 on jailbreaking the PS3 is really fun, and they discuss this in detail.”
— pdkl95, Dec 2015, in “Developer claims 'PS4 officially jailbroken'”

What HN commenters said

3 Hacker News comments link this video. Each one links back to its thread.

pdkl95Dec 2015Recommends

DRM does not require a closed/controlled ecosystem. The best protection against the development of game-copying modchips on the PS3 was the ability to run Linux on it as an official feature. The serious jailbreaking (which necessarily allowed game-copying) was done only after they pissed off the "other os" crowd by removing it in a later patch. (the fail0verflow's talk[1] at 27C3 on jailbreaking the PS3 is really fun, and they discuss this in detail. (also: as discussed about 35min into [1], using the same nonce for the ECDSA signature of every game? So the keys can be derived from two games, without knowing most of the curve parameters? What was Sony thinking?!) [1] ▶ this video

in “Developer claims 'PS4 officially jailbroken'” · View on HN

nemothekidJan 2014Cites it

The PS3 only went uncracked for so long because Sony offered the option to install Linux on the PS3. Once Sony removed that option the people with the smarts to crack the PS3 did so. Once a magnifying glass was put under the PS3 it turned out that the "DRM" was actually horribly implemented (like Rand() functions that were essentially returning constants). ▶ this video

in “Requirements for DRM in HTML are confidential” · View on HN

rkallaJun 2011Cites it

More or less. 1. Sony removes "Install Other Operating Systems" option from the PS3 OS. 2. Out of frustration at corporate policy for REMOVING major features from hardware/device paid for and owned by millions, the hackers start working. 3. Months later, GeoHot releases (what I understand to be) the root private encryption keys for the device. 3.5 (forgot this) fail0verflow group circumvents the PS3's security system using this work from GeoHot - ▶ this video 4. Other hacking groups, now with the keys to the kingdom, begin working on hacking the PS3 to allow the installation of any software, not just officially released/signed/blessed releases. This results in a "jailbreak" for the PS3, much like what jailbreaking does to the lock-down security on an iPhone. (This is when things start to go south) 5. A technique for loading your own software onto the PS3, circumventing the system's security checks comes out. (Now the door to pirating PS3 games is open. Download images, burn the Blu-rays, pop them in the PS3 and play). 6. Another hacking group, using some portion of this manipulation, actually manage to get their PS3's logged into the private developer-based PSN network (it's a full copy of the real PSN network specifically for developers actively working on titles that need to test things like updates or addon downloads/installs). 7. It is discovered that the PSN-Dev network does not do real credit card authentication before items are purchased and downloaded. So for example, if I

in “Sony Music Brazil hacked ” · View on HN

Topics & tags

Security & hackingSpeedrunning, glitches & game hackingCryptographyps3ecdsajailbreakfail0verflowreverse engineering