@beanclr and andutrache: It's the ACT.DAT file that is generated with the internal OpenPSID and the unique ID (an hardware offset).
The ACT.DAT file is only needed to verify valid LICENSE files (with the .rif extension), but since we don't want to verify the files, we can just ignore this and assume all users have access to any DLC content.
All we need next is to properly emulate the decryption routine, which takes place after the license verification step.
Of course, if we're talking about forging DRM data, this would require proper licensing forging. Even so, this may still be possible to emulate to some extent, but the functions used to generate the ACT.DAT file (scePcactAuth1BB and scePcactAut21BB from openpsid.prx, used by the np_inst.prx module) will need a fake PSN ID, which I'm still working on.
The ACT.DAT file is only needed to verify valid LICENSE files (with the .rif extension), but since we don't want to verify the files, we can just ignore this and assume all users have access to any DLC content.
All we need next is to properly emulate the decryption routine, which takes place after the license verification step.
Of course, if we're talking about forging DRM data, this would require proper licensing forging. Even so, this may still be possible to emulate to some extent, but the functions used to generate the ACT.DAT file (scePcactAuth1BB and scePcactAut21BB from openpsid.prx, used by the np_inst.prx module) will need a fake PSN ID, which I'm still working on.