Originally Posted by zadow28
Im also looking into the dongle, but i have to see what it does with the cfw also.How they communicate., els we crack the dongle they just change key and cfw. We have to cover all parts.
I have seen indications of master keys not just 3.6+ many have talked about it before.
But have seen alot of it mention digging into dongle stuff.
Off cause i cant find or prove it 100%
.but it says on the first post master key.And it also tell me thats why trueblue are still here after alot of OFW updates from sony
|
Exactly. If they have private keys from say 3.6+ (3.7,4.11,etc) then there is nothing Sony can do! There have been various methods discussed on how to get thoes keys using hardware. So realistically thats the only thing that would make sense. Otherwise like you have said, their method/exploit would have been blocked.
Now what this means is, what keys are actually on the dongle? I would guess they would be as dumb as leaving say 4.11 private/master key on the dongle. If this is the case then there would be no real need to release eboots regularly. You could have the dongle take care or decrypting with 3.6+ key and re-encrypting with 3.55 keys.
Its most likely the case that they decrypt the 3.6+ eboots on a computer. then encrypt them with there TB encrypt keys(possible the "master key" from your dumb). This is essentially the drm, so if we were able to get the actual keys from the dongle, we could decrypt the eboots, and sign them with 3.5 keys so they would work with current cfw.
The problem with that is that they can update the TB and the keys would have to be retrieved again. So we really would still need 3.6+ keys themselves. At that point we can have our new cfw(in which case the eboots would really matter)