I recently installed Ferrox 4.87 (never used CFW before) and it leads me to a question that I could not find a 100% accurate answer so... In CFW scenario, is there any need to resign anything? If yes, could you please list here?
Example:
- Play ISO's = needs resign
- any pkg needs resign
I don't know If I made my point but... let's see what happens!
Thanks for fast reply @Berion but I still in doubt:
1. Are you saying that ISOs from my backups doesn't need to resign because when I ran them on my PS3 means that is was already signed?
2. pseudoretail? All current packages are ok? Well I really didn't understand that. Could you elaborate?
3. Any PKG that is not from official PSN (like tools, emulators, PSX games, homebrews, etc) do not need to be resigned, is that correct?
If disc images was created from original discs, or if was created from data copied from original discs without any modifications then You don't need resign anything today or in future.
If You found "bad signed" eboot or package, error number will tell You what is wrong (because You will not be able to install it and/or run it). https://www.psdevwiki.com/ps3/Error_Codes
Every package which comes from Sony and was never edited by You or someone else, does not need to be resigned today, past and in future. Packages with ancient homebrew must be resigned/repacked.
But after reading again I didn't understand why custom PKG like webMAN, PKGi, etc does not need to be resigned. How ps3 tell it's a valid pkg and you are able to install?
I know it sounds very noob but... that's what I'm XD
If the game was published in physical format (bluray disc) then the signed files are the EBOOT, optionally SELF, SPRX and other "fake" file extensions used by the game company
Lets say... are "executable files"... like the file extension .EXE in microsoft windows
With "fake" file extensions i mean... the game developers can include a file inside the game named FILE.XIIPE
The file extension .XIIPE is something the game developers invented (but that file could be a .SELF with the file exension renamed)
The game developers have freedom to do this kind of renamings, so sometimes is hard to find which files are "executables"
If the game was released as digital format (PKG), the same rules applyes, but additionally the PKG container itself uses another signature
----------------
That signatures "made by sony" are unique, we (the PS3 scene) are not able to replicate them
What we do is some kind of "pseudo signature" that doesnt follows strictly the official signatures "made by sony"... is something different and eventually could be problematic
Lets say... now you are in HEN and you decide to resign files (with some resigning method that works in HEN)... but eventually a new exploit is released that allows you to install CFW and the files you resigned could be invalid for the new CFW... because the signature you used is not completly legit
Another example... you take a game that was published in 2008, when the only PS3 firmware version available was 1.00... well... the files (and PKG incase is a digital release) are signed with the keys from firmware 1.00... but that signature is "made by sony" so is going to work in any firmware version... of course it works in firmware 1.00 but also in 4.87... or firmware 6.66... or firmware 9.99
If you want to prevent this kind of problems the best we can do is to dont resign anything, this way we are preserving the files "signed by sony"
------------------------
With homebrews this rules doesnt applyes because none of the homebrews are "signed by sony"
And as mentioned before, we cant mimick that signatures "made by sony"
There are many old homebrews that was signed years ago using signatures that are invalid nowadays... in that case the only thing we can do is to resign them (and/or repack them incase is a PKG)
Humm... let me tell you what's in my head after reading all over again:
- PS3 itself does not start the license validation.
- The game itself starts the license validation.
- In terms of executing/installing/validating games, CFW does not provide any advantage over HEN or OFW.
- No homebrew (even in PKG format) needs to be resigned.
I still in doubt about:
1. Games that runs on emulator, like PSX games, needs to be resigned?
2. What happens if, by mistake, I reassign an original game (assigned by sony)?
Humm... let me tell you what's in my head after reading all over again:
- PS3 itself does not start the license validation.
- The game itself starts the license validation.
- In terms of executing/installing/validating games, CFW does not provide any advantage over HEN or OFW.
- No homebrew (even in PKG format) needs to be resigned.
I still in doubt about:
1. Games that runs on emulator, like PSX games, needs to be resigned?
2. What happens if, by mistake, I reassign an original game (assigned by sony)?
It's simple, don't resign anything. If a game don't work, redump it from disc. If it's a pkg, download it again (from $ony or from the homebrew maintainer). It's rare when somebody needs to resign a game or homebrew. If you find an old homebrew that needs resign, ask for help here.
About your questions:
1. PS1, PS2 and PS3 ISO never need to resign.
2. The game will probably not work.
Edit: Only on HEN, PS2 games need to be encrypted.
