[NEWS] Rilasciato Bluedisk CFW 4.21(con spoof 4.25),LV0 Keys e Rogero CFW 4.21 CEX

[Titty]

In teoria la recuperi perchè è un brick parziale

[Dexther]

Noob mode disinteressato ON.
Ma ora con questo metodo posso farci di tutto senza problemi di sorta ?

[Cracco]

Una domanda,è possibile farsi il backup della nor partendo dal CFW 4.21?Perchè con il metodo del tutorial non funziona ,in pratica una volta installato il FactoryServiceMode.gnpdrm questo non si avvia.

[Titty]

No... l' unico metodo è quello riportato sul tutorial. Ma non va in che senso? NON fa il backup? Oppure non lo visualizzi?

[Cracco]

Una volta avviato il PKG factory service mode da errore (80010017) all avvio

[Titty]

Ma l'hai fatto da 4.21?
Prob nn è compatibile... infatti lo facciamo fare prima

[Cracco]

Si immaginavo,proprio perchè non l'ho fatto prima pensavo si potesse fare con qualsiasi CFW.Era piu per una questione di sicurezza ,se in futuro esce qualche altro tool bene altrimenti spero solo che non debba servirmi.Thx
Magari se vuoi aggiungerlo nel tutorial che non è compatibile con il 4.21 cosi altri non incappano in questa svista.

[Titty]

Appena ho modo farò l' aggiunta.

[Razorbacktrack]

Vediamo ora come uscire dal limbo/CFW Rogero 4.21.

Ho letto che il metodo di Rogero per tornare a 3.55 non funziona (anche se sinceramente non ho avuto la possibilità di provare) :/

Spero con un nuovo firmware si risolve la situazione

[Titty]

Il qa flag non riesce a far tornare indietro?

[Razorbacktrack]

Credo che devi averlo abilitato prima di installare il CFW : [url=http://www.tortuga-cove.com/forums/viewtopic.php?f=127&t=3636&start=250]Tortuga Cove • View topic - Rogero CEX-4.21 CFW v1.00 Free for All[/url]

[Cracco]

Scusa Razor ma perchè hai avuto problemi con questo CFW o solo per capire se si puo tornare indietro?

[Razorbacktrack]

Attualmente la mia unica PS3 ha sopra il 4.20 dex ,ancora non ho provato questo firmware.

Comunque era solo per capire se si può tornare indietro; mi sta sembrando la stessa situazione di quando hanno fatto un firmware ibrido 3.55/3.60 (il firmware di Naima) che se ricordo bene ,dopo l'installazione,perdevi la possibilità di tornare al 3.55,ma non sto ricordando se si poteva aggiornare con un firmware originale superiore per poi fare il downgrade via hardware (forse in quel periodo nemmeno c'era questa possibilità xD)

[Cracco]

Ok,grazie,quindi per ora una l'ho moddata al 4.21 ,per le altre che ho aspetterò gli sviluppi.

[Baccello]

Ma sono l'unico che sta ancora aspettando ad installarlo?

[Cracco]

io l'ho installato e fin'ora non ho problemi,il problema sarà casomai se bisognerà aggiornare o reinstallare un ipotetico futuro custom firmware se bisognerà ripassare dal 3.55............ma magari saranno usciti altri tools o altre strade.

[MaX7o]

Ma sono l'unico che sta ancora aspettando ad installarlo?

Io aspetterei visto che cè in uscita anche il CFW del team Rebug a detta loro priva da rischi di brik.

[Titty]

Che parolone... privo di rischi brick... il brick è semprpossibile basta poco... anche un calo di tensione o un traferimento errato di dati dalla penna...

[xboxbs]

un po' di arabo direttamente da Marcan (fail0verflow), in sintesi le chiavi scoperte sono del bootldr (e non lv0)

One of fail0verflows devs Marcan speaks of the new lvl0 leak:

by marcansoft (727665) on Tuesday October 23, @09:04PM (#41747075) Homepage

The first-stage bootloader is in ROM and has a per-console key which is effectively in tamper-resistant silicon. The second-stage bootloader (bootldr) is encrypted with the per-console key, but is not upgradable and is the same for all consoles (other than the encryption wrapper around it). This second-stage bootloader verifies lv0. Sony signed lv0 using the same broken process that they used for everything else, which leaks their private key. This means that the lv0 private key was doomed from the start, ever since we demonstrated the screwup at the Chaos Communication Congress two years ago.

However, because lv0 is also encrypted, including its signature block, we need that decryption key (which is part of bootldr) before we can decrypt the signature and apply the algorithm to derive the private key. We did this for several later-stage loaders by using an exploit to dump them, and Geohot did it for metldr (the “second root” in the PS3′s bizarre boot process) using a different exploit (we replicated this, although our exploit might be different). At the time, this was enough to break the security of all released firmware to date, since everything that mattered was rooted in metldr (which is bootldr’s brother and is also decrypted by the per-console key). However, Sony took a last ditch effort after that hack and wrapped everything after metldr into lv0, effectively using the only security they had left (bootldr and lv0) to attempt to re-secure their platform.

Bootldr suffers from the same exploit as metldr, so it was also doomed. However, because bootldr is designed to run from a cold boot, it cannot be loaded into a “sandboxed” SPU like metldr can from the comfort of OS-mode code execution (which we had via the USB lv2 exploit), so the exploit is harder to pull off because you don’t have control over the rest of the software. For the exploit that we knew about, it would’ve required hardware assistance to repeatedly reboot the PS3 and some kind of flash emulator to set up the exploit with varying parameters each boot, and it probably would’ve taken several hours or days of automated attempts to hit the right combination (basically the exploit would work by executing random garbage as code, and hoping that it jumps to somewhere within a segment that we control – the probabilities are high enough that it would work out within a reasonable timeframe). We never bothered to do this after the whole lawsuit episode.

Presumably, 18 months later, some other group has finally figured this out and either used our exploit and the hardware assistance, or some other equivalent trick/exploit, to dump bootldr. Once the lv0 decryption key is known, the signing private key can be computed (thanks to Sony’s epic failure).

The effect of this is essentially the same that the metldr key release had: all existing and future firmwares can be decrypted, except Sony no longer has the lv0 trick up their sleeve. What this means is that there is no way for Sony to wrap future firmware to hide it from anyone, because old PS3s must be able to use all future firmware (assuming Sony doesn’t just decide to brick them all…), and those old PS3s now have no remaining seeds of security that aren’t known. This means that all future firmwares and all future games are decryptable, and this time around they really can’t do anything about it. By extension, this means that given the usual cat-and-mouse game of analyzing and patching firmware, every current user of vulnerable or hacked firmware should be able to maintain that state through all future updates, as all future firmwares can be decrypted and patched and resigned for old PS3s. From the homebrew side, it means that it should be possible to have hombrew/linux and current games at the same time. From the piracy side, it means that all future games can be pirated. Note that this doesn’t mean that these things will be easy (Sony can obfuscate things to annoy people as much as their want), but from the fundamental security standpoint, Sony doesn’t have any security leg to stand on now.

It does not mean that current firmwares are exploitable. Firmware upgrades are still signed, so you need an exploit in your current firmware to downgrade. Also, newer PS3s presumably have fixed this (probably by using newer bootldr/metldrs as trust roots, and proper signing all along).

….

The keys are used for two purposes: chain of trust and chain of secrecy. The compromise of the keys fully compromises the secrecy of the PS3 platform permanently, as you can just follow the links down the chain (off-line, on a PC) and decrypt any past, current, or future firmware version. Current consoles must be able to use any future firmware update, and we now have access to 100% of the common key material of current PS3s, so it follows that any future firmware decryptable by current PS3s is also decryptable by anyone on a PC.

However, the chain of trust can be re-established at any point along the line that can be updated. The chain of trust is safely rooted in hardware that is near impossible to modify (i.e. the CPU’s ROM and eFuse key). The next link down the chain has been compromised (bootldr), and this link cannot be updated as it is specific to each console, so the chain of trust now has a permanent weak second link. However, the third link, lv0, can be updated as it is located in flash memory and signed using public key crypto. This allows Sony to secure the entire chain from there onwards. Unless you find a vulnerability in these updated links, you will not be able to attack them directly (applications, e.g. homebrew software, are verified much further down the chain). The only guaranteed way to break the chain is to attack the weak link directly, which means using a flash writer to overwrite lv0. Once you do so, the entire chain collapses (well, you still need to do some work to modify every subsequent link to turn off security, but that is easy). If you have old firmware, you have at least some other weak links that, when compromised, allow you direct access to break the bootldr link (replacing lv0), but if you run up to date firmware you’re out of luck unless you can find a weakness or you use hardware.

Old PS3s are now in the same boat as an old Wii, and in fact we can draw a direct comparison of the boot process. On an old Wii, boot0 (the on-die ROM) securely loads boot1 from flash, which is securely checked against an eFuse hash, and boot1 loads boot2 but insecurely checks its signature. On an old PS3, the Cell boot ROM securely loads bootldr from flash, which is securely decrypted and checked using an eFuse key, and then bootldr loads lv0 but checks its signature against a hardcoded public key whose private counterpart is now known. In both cases, the system can be persistently compromised if you can write to flash, or if you already have code execution in system context (which lets you write to flash). However, in both cases, you need to use some kind of high-level exploit to break into the firmware initially, particularly if you have up-to-date firmware. It just happens that this is trivial on the Wii because there is no game patch system and Nintendo seems to have stopped caring, while this is significantly harder on the PS3 because the system software has more security layers and there is a game patch system.

….

The name is presumably wrong – they would be the bootldr keys, as the keyset is considered to “belong” to the entity that uses those keys to check and decrypt the next thing down the chain – just like the metldr keys are the keys metldr uses to decrypt and verify other *ldrs, the bootldr keys are the keys bootldr uses to decrypt and verify lv0.

Anyway, you’re confusing secrecy with trust. These keys let you decrypt any future firmware; as you say, if they were to “fix” that, that would mean new updates would not work on older machines. However, decrypting firmware doesn’t imply that you can run homebrew or anything else. It just means you can see the firmware, not actually exploit it if you’re running it.

The only trust that is broken by this keyset (assuming they are the bootldr keys) is the trust in lv0, the first upgradable component in the boot process (and both it and bootldr are definitely software, not hardware, but bootldr is not upgradable/replaceable so this cannot be fixed). This means that you can use them to sign lv0. Period. Nothing more, nothing less. The only things that these keys let you modify is lv0. In order to modify anything else, you have to modify everything between it and lv0 first. This means that these keys are only useful if you have write access to lv0, which means a hardware flasher, or an already exploited console, or a system exploit that lets you do so.

….

Oh, one more thing. I’m assuming that these keys actually should be called the bootldr keys (as in the keys that bootldr uses to verify lv0), and that the name “lv0″ is just a misnomer (because lv0 is, itself, signed using these keys).

If this keyset is just what Sony introduced in lv0 after the original hack, and they are used to sign everything *under* lv0 and that is loaded *by* lv0, then this whole thing is not newsworthy and none of what I said applies. It just means that all firmwares *to date* can be decrypted. Sony will replace this keyset and update lv0 and everything will be back at step 1 again. lv0 is updatable, unlike bootldr, and is most definitely not a fixed root of trust (unlike metldr, which was, until the architecture hack/change wrapped everything in lv0). If this is the case, color me unimpressed.

…..

by marcansoft on Wednesday October 24, @01:04AM (#41748707) Attached to: PS3 Encryption Keys Leaked

Nevermind, I just checked. They are indeed the bootldr keys (I was able to decrypt an lv0 with them). Consider this confirmation that the story is not fake.

[Razorbacktrack]

Si,lo stavo leggendo ma dopo non ce l'ho fatta più xD