Handy Dandy PS3 Key Spreadsheet

[inf1]

and what does that mean for the end user? Does that hinder the devs to get CFW out?

CFW - you mean 3.50/3.55 jailbroken PUP? well, its possible now, but you still need time, to find what you need to patch, to sign files, to pack them, to test it. it will take some time.

[Tiglet]

CFW - you mean 3.50/3.55 jailbroken PUP? well, its possible now, but you still need time, to find what you need to patch, to sign files, to pack them, to test it. it will take some time.

Ye, but will we be able to use the PUP without the retarted dongles? I mean cant we just upload the file to a USB stick, like we would with any other firmware update, and install it without having to jailbreak the console with an overpriced dongle?

[vidarino]

Listen, it's not just about signing the application. One would think people realized this by now, but here goes:

The jailbreak isn't just a backup manager. The USB exploit payload also patches the lv2 kernel with a couple of new syscalls, most notably one that remaps a game directory over the BD directory, i.e. spoofing the contents of the disc. Without that function in place, a backup manager is worthless. And you can't just add said kernel patching to any old application, as the kernel does not allow regular applications that kind of access.

That said, in terms of progress, it's been an amazing couple of days, so hopefully it won't be long before we can grab a custom firmware with a pre-patched 3.55 kernel. (The peek/poke syscalls alone should suffice, I believe. Then the app *could* do the rest of the patching itself.)

Also, all the dongle manufacturers must be freaking out by now. ;-) (Granted, the ones can that can be reflashed as service jigs might come in handy for a while still, while downgrading and re-flashing might be necessary.)

[dread123]

just to confirm is this spreadsheet now verified? as there have been a lot of key changes overnight?

good work to erveryone involved

[webstersx]

because you need at least two different files that was encrypted with same key to calculate private, and unfortunately there is only lv1.self that was encrypted with lv1ldr keys.

and what does that mean for the end user?

+1 -- what's the implication of not having private keys for lv1ldr?

[openps3]

Here all keyfiles ziped

[openps3]

All files can Download from SHA1 Hashes - OpenPS3

No self create need

Don't bee a

[Elaugaufein]

+1 -- what's the implication of not having private keys for lv1ldr?

Assuming the sheet is accurate and there's enough lvl1 files to get the key for 3.42 and earlier (and I'm not saying this is true, I've only just started looking at this and haven't even unpacked a PUP yet) not a lot, given that you can still use the public key to decrypt 3.50/3.55 , and then modify each file (even the lvl1 files) so they all accept earlier keys and then resign them with an earlier key (basically all that matters is that your key verification and signing are consistent).

If the sheet is incomplete and even 3.42 and earlier are underivable , the implication would be that you can't sign lvl1 files (the files that make up the hypervisor), so although you could replace gameOS (since you've got the keys to make lvl2 stuff look proper to its loader) you couldn't replace the hypervisor (since lvl1ldr won't accept the signatures), but I believe that compromising metldr (ie having the metldr private key) allows compromising lvl1 anyway since you can use that to compromise lvl1ldr and then compromise lvl1 that way.

[Tiglet]

Assuming the sheet is accurate and there's enough lvl1 files to get the key for 3.42 and earlier (and I'm not saying this is true, I've only just started looking at this and haven't even unpacked a PUP yet) not a lot, given that you can still use the public key to decrypt 3.50/3.55 , and then modify each file (even the lvl1 files) so they all accept earlier keys and then resign them with an earlier key (basically all that matters is that your key verification and signing are consistent).

If the sheet is incomplete and even 3.42 and earlier are underivable , the implication would be that you can't sign lvl1 files (the files that make up the hypervisor), so although you could replace gameOS (since you've got the keys to make lvl2 stuff look proper to its loader) you couldn't replace the hypervisor (since lvl1ldr won't accept the signatures), but I believe that compromising metldr (ie having the metldr private key) allows compromising lvl1 anyway since you can use that to compromise lvl1ldr and then compromise lvl1 that way.

and what does the hypervisor do exactly, I mean what can it prevent us from doing ? Sorry for noob question probably, but you seem to know a bit about this!

[Elaugaufein]

Basically no existing official PS3 game or application (or OtherOS in its original form) has access to the hypervisor at the level that key would provide so ...

I don't think it does anything relevant to an end user in its current state, the hypervisor is fairly removed from the end user (the end user interacts with lvl2 or with apps that sit between lvl2 and the user) and the PS3 hypervisor doesn't perform functions like verifying that lvl2 code hasn't been tampered with or that code that lvl2 is running is properly authorized that could make it relevant to an end user. But since as I said I've only just started looking at the technical side of this I could be wrong.