|
|
#1 |
|
Apprentice
![]() Join Date: Aug 2012
Posts: 21
Likes: 4
Liked 2 Times in 1 Post
Mentioned: 3 Post(s)
Tagged: 0 Thread(s)
|
klicensee from retail pkg?
Anyone knows how to extract the klicensee from a retail pkg? (at offset 0x70-0x7F)
All of the tools are using the old script to extract the klicensee from a DEBUG pkgs, and this is not correct for a retail pkgs. |
|
|
|
|
|
#2 |
|
Senior Member
![]() Join Date: Dec 2010
Posts: 2,033
Likes: 1,031
Liked 580 Times in 471 Posts
Mentioned: 237 Post(s)
Tagged: 0 Thread(s)
|
could be wrong info, i think for retail.pkg's either use pkgcex2dex" and drop the retail pkg into the box..write down k_licensee and repack using the key, checking the pkg for it in hex the klicensee isn't find there at offset 70, only the QA digest at offset 60
another way is that klicensee python script, atleast both tools report same (real?)"retail" klicensee..check screenshot howto find this without any tool..beats me.. ![]() edit @noinok12 ok..i see..so whatever its putting there is a fake key....thx for the info.. Last edited by haz367; 11-26-2012 at 03:42 PM. |
|
|
|
|
|
#3 |
|
Apprentice
![]() Join Date: Aug 2012
Posts: 21
Likes: 4
Liked 2 Times in 1 Post
Mentioned: 3 Post(s)
Tagged: 0 Thread(s)
|
This python script is only for debug pkgs (made with make_package_npdrm or psn_package_npdrm), and it's not valid with retail pkgs.
PkgCexToDex uses this script...
|
|
|
|
|
|
#4 |
|
Senior Member
![]() Join Date: Dec 2010
Posts: 2,033
Likes: 1,031
Liked 580 Times in 471 Posts
Mentioned: 237 Post(s)
Tagged: 0 Thread(s)
|
oh..that's a bummer...it looked real
..damn...i like to know to then ..bumping this and hope someone pops-up with some info
|
|
|
|
|
|
#7 |
|
Senior Member
![]() Join Date: Dec 2010
Posts: 2,033
Likes: 1,031
Liked 580 Times in 471 Posts
Mentioned: 237 Post(s)
Tagged: 0 Thread(s)
|
edit...
nvm...i'm only another dumbass that occasionally repacks a pkg and then use apparently a fake/debug pkg klicensee reported by either that script or pkgcex2dex, atleast all installed retail pkg's have a random klicensee instead of only 00000 wich also doesn't matter really then again if it reports a fake/debug klicensee it's useless in that way..agreed.. it's nice info to know howto get real retail pkg klicensee then, or i totally don't get what ur trying to achive..in that case nvm my reply's
Last edited by haz367; 11-27-2012 at 06:15 AM. |
|
|
|
|
|
#8 |
|
Apprentice
![]() Join Date: Aug 2012
Posts: 21
Likes: 4
Liked 2 Times in 1 Post
Mentioned: 3 Post(s)
Tagged: 0 Thread(s)
|
I think the klicense in the header of debug pkgs or with drmtype=free is pretty useless... , i only want a new way to obtain the klic when it's obfuscated/encrypted/generated in the elf. Unfortunately, now we do not have access to official debug pkgs.
I'm working in the RockBand songs. In the patch updates there are a file band_s.self, that need a game klicense for decryption/encryption. This klicense (easy to obtain) isn't the song klicense needed for calculate the headerhash in the edat inside the songs. My theory is that this exclusive song-klicensee is generated by the eboot, probably is unique for each song, and must be in the header of the pkg songs. If anyone knows anything about this theme, please tell me something. Regards. Last edited by noinok12; 11-27-2012 at 08:00 AM. |
|
|
|
![]() |
| Bookmarks |
| Thread Tools | |
|
|