Originally Posted by DEFAULTDNB
Thanks for the info
, you always seem to know everything
Nah i just asked the right questions, this is not from myself but from other devs. Contrary to what's been said, they do share if you ask proper questions. I don't know everything
If they didn't fix it, it could be exploited (in theory) as follows.
vsh stores the version of your eboot when you install a game update.
- So let's says we have BLUS30838 (COD:MW3) disc
- and installed a npdrm-package on harddisc, version 9.99
- This number and stuff from the SFO in the package is stored during installation.
- When you launch the disc, it checks with vsh if you have a higher update -> yes 9.99
- It runs the eboot from the update instead
- So we don't touch eboot.bin from the update, otherwise it will not run
- But, we decrypted it on PC and know the klic key..
- in the update folder we replaced default_mp.self with say, ftpserver.self, renamed as default_mp.self, and signed as npdrm with the klic key that eboot.bin expected.
In this situation, you could in theory upgrade to 3.56. then launch your original COD:MW3 disc. The system would run & check the eboot from your harddisc, this works since it's untouched. Then choose multiplayer from the main menu -> modfied default_mp.self is launched -> ftp server starts instead.
Again it's not usefull since they thought about this and changed npdrm in 3.56+ so we can't exploit it like this for >3.56
And, you need hardware flasher to go back to <=3.55 to keep enjoying the benefits of lower fw's.