1 day after = new FW => patched from day1

1 day after = new FW => patched from day1

Are you stupid how are they going to patch this with a new firmware they cant block signed code can they.

If they block signed code previous games and maybe even stuff like controllers would not work.

The only possible way to patch it is if they implement a new signature which i don't even think is possible as the system would have to be modified.

new work package This is how Sony will likely respond, if they feel the effort is worth the result. It's quite an effort, and the result .. well.

1) Respin the hardware. There's an incredible exploit in that the verification of bootloaders loaded off the NAND/NOR is verified after they've been loaded, and then they're allowed to continue to execute. This is why ALL EXISTING PS3s on the market are from now on hackable. Really. There's nothing that can be done to stop this.

2) Design new firmware(s) that contains the infamous "whitelist" of all previously (and erroneously) signed software, but with new keys and new signature verification algorithms. Deploy these firmwares/loaders ONLY on the respinned hardware (see above).

3) For older hardware (that is, everything already produced from the factory and on the market) release new firmware that contains the new signature verification algorithms, but NOT any of the new keys. Remember, what you deploy on the old hardware is fully transparent. Update the loaders as well, as talked about in the presentation, since that will force everyone who wants to have a still jailbroken console to install a modchip (see #1).

4) Dual-sign all new stuff. Old broken consoles will be able to run it, and the new secure model will verify with new keys. Previously signed software will only execute on the new systems if they pass the whitelist-test.


... so, this would be quite an effort, and quite expensive. It should restore chain of trust on the new systems, and the new signing key shouldn't be leaked. I _think_ the whitelisting should succeed then as well.

Success? Well, that still leaves all produced PS3s to date completely broken, and also able to run all new software. Only the new systems will be "homebrew-free". Modchip-installers will be happy though, NOR/NAND replacements aren't for the faint hearted to install. And, all this with the assumption that Sony will find and close ALL existing holes in one try. Not likely.

(Comments on my logic from those who understood the presentation welcome)

As far is I understand the earliest patch is in lv2ldr (no access to lv1ldr plaintext = no key = no lv1 access yet). However, what they state is that IF Sony manages to update the loaders to remove the lv2ldr exploit (which is a proper buffer overflow) they can just use a modchip to run the old version of it and gain access right back (and that will always work since metldr, which verifies and loads lv2ldr, is not updateable).

That is, whatever you happen to do with your broken PS3 the chain of trust is gone and you can always root the current hardware. It will require a modchip in the worst case scenario though, and if you're careful and don't allow, by choice or by mistake, the loaders to get updated you're fine with a software/firmware hack only.

That's just what I've heard from a few people.

Maybe this is how TheUnkown and hunter did it.

I know i forgot the exact quote of it but it was hilarious.