[DEFAULTDNB]

I have heard chatter of people trying to make 3.60 cfw, 3.60 signed tools, 3.60 downgraders (software) @cotojestwtf said the priv keys got leaked too, no idea if its legit.

[Gonzakpo]

Originally Posted by ryant001 I think we can simply sign with the keys that we do have(<=3.55).

So, you say decrypt using 3.60, modify it and reencrypt with 3.55 keys. I have no idea if that is possible. What I fail to understand is:

1) Now the loaders are inside the lv0.
2) The loaders check the integrity of the things they load (lv1, lv2, app, etc).
3) If you modify the lv2 for example, and reencrypt it. Then you still need to make the lv2ldr believe that it was not modified. But the problem is that you don't have access to it because you can touch the lv0 ("the ultimate barrier" :P).

So, I personally don't think this will lead to a new CFW unless somebody releases the lv0 or the bootloader keys. BUT, I do think this will allow hackers to find new exploits. So, all in all is a great release but I doubt we will see a CFW (for 3.56+ users, that is). My bet is that this will lead to something more like the Kakarotoks HEN. But those are just my personal guesses.

[hellsing9]

Originally Posted by Gonzakpo So, you say decrypt using 3.60, modify it and reencrypt with 3.55 keys. I have no idea if that is possible. What I fail to understand is: 1) Now the loaders are inside the lv0. 2) The loaders check the integrity of the things they load (lv1, lv2, app, etc). 3) If you modify the lv2 for example, and reencrypt it. Then you still need to make the lv2ldr believe that it was not modified. But the problem is that you don't have access to it because you can touch the lv0 ("the ultimate barrier" :P). So, I personally don't think this will lead to a new CFW unless somebody releases the lv0 or the bootloader keys. BUT, I do think this will allow hackers to find new exploits. So, all in all is a great release but I doubt we will see a CFW (for 3.56+ users, that is). My bet is that this will lead to something more like the Kakarotoks HEN. But those are just my personal guesses.

No cfw, no mfw.

[DEFAULTDNB]

take a tool signed for 3.55, sign it for 3.60, use it on 3.60-3.61.

Without peek and poke we wont have backup managers but maybe the NPDRM method like making an XMB PSN style loader, like back in the days of GHCFW.

[Gonzakpo]

Originally Posted by DEFAULTDNB take a tool signed for 3.55, sign it for 3.60, use it on 3.60-3.61. Without peek and poke we wont have backup managers but maybe the NPDRM method like making an XMB PSN style loader, like back in the days of GHCFW.

But we don't have the private keys of 3.60!!! We can't sign anything!!

Unless there's something I'm missing.

[carldenning]

Originally Posted by DEFAULTDNB take a tool signed for 3.55, sign it for 3.60, use it on 3.60-3.61. Without peek and poke we wont have backup managers but maybe the NPDRM method like making an XMB PSN style loader, like back in the days of GHCFW.

ive tried that on dex 4.11 and only a few games would work ,

[DEFAULTDNB]

if we can decrypt 3.60 it stands to reason we can reverse the process and encrypt.

Why not take showtime for example, and re-sign it from 3.55 to 3.60 with the keys we are using to decrypt 3.60 eboots?

Am I wrong here?

[Gonzakpo]

Originally Posted by DEFAULTDNB if we can decrypt 3.60 it stands to reason we can reverse the process and encrypt. Why not take showtime for example, and re-sign it from 3.55 to 3.60 with the keys we are using to decrypt 3.60 eboots? Am I wrong here?

You are talking about two different keys. The one that decrypts is the public key. And the one that encrypts is the private key. The console has the public key only. The private key is secret and kept by Sony. The thing is that by some silly mistake by Sony previous private keys were able to be calculated easily. Now that's not a possibility as far as I know.

Yes, you can decrypt things and study them to find exploits. No, you can't encrypt things with the public key.

PS: We are brainstorming here. I could be wrong. So please take my words with caution.

[Persian McLovin]

With the keys that are now out in the wild, surely there is the chance of a software downgrade from 3.60 to 3.55?

[pois0n]

Originally Posted by abdelkarim We only need a software downgrade solution. I have 2 questions : is it really possible ? or just speculation ? My second question is : who are (or is) the dev with enough skills (& not blinded by the $$$) to do it ?

Software downgrade would be nice but those stuck on 3.56+ would still have no solution