Originally Posted by rayan2
but will the trophies work ??
|
No, it will not work with the current public version. I will release a new version soon but without trophy keys. See my posts about it because I already explained why I think so.
Originally Posted by Wouldy
Shouldn't all the hashes be ok.
I have attached a log of the problem, since the code wrap on this forum is messy and buggy.
|
I think it is an issue with 4 version. Can you check the byte at offset 0x0F at PARAM.PFD? If it is 4 then it seems that they have different keys or maybe algorithm for this version. I will try to investigate it soon.
Originally Posted by aldostools
Well I use a slightly different method in my work in progress of the GUI
|
Wow
Your tool is great.
Originally Posted by aldostools
I still don't get the "update" PFD to work properly... maybe master
@flatz
could give a hand
|
What are your problem, aldostools? I can help you.
Let me say a few words about the process of signing. There are two types of files - system file object (PARAM.SFO) and game files (which are encrypted by the secure file ID). The first one contains 3 or 4 hashes (depending on whether it is a trophy file database or not). So for game saves they are a static key embedded in the prx module, your unique console ID, disc hash key and authentication ID (it is static too). So if you take a foreign save game you probably don't have its console ID and the disc hash key (you can only take a disc hash key if you have an original game disc for it). Also if you don't have a secure file ID and you are lazy to get it (by bruteforcing it/reversing the game executable/dumping from the memory) then you can't calculate hashes for game files too. That's why I created two different modes of signing/checking - one for these people who want only to resign a foreign save game and nothing more and the second one is for people who have all data to update all hashes for their save game. The first mode called partial update/check (see the corresponding option at pfdtool), and for full update you don't need to specify this option. The partial update only updates hashes which are easy to calculate (based on static data such as authentication ID and console ID). So if you have a filled global.conf (all keys and your console ID) and run a partial update on the foreign save game to resign it for your console then you got a fully working resigned save game. But if you want to modify save game files which are encrypted then you need to get all data and specify them in configuration files and then use a full update to resign it. By the way the PS3 itself doesn't check some hashes such as a hash which was calculated using a disc hash key. So you can omit some of them (I only omitted the hash which I said and it works fine). But I don't know what situation will be in the future, maybe S0ny will add a check for them.