View Single Post
Old 11-05-2011   #55
tiefputin2
Member
 
Join Date: Apr 2011
Posts: 62
Likes: 0
Liked 39 Times in 22 Posts
Mentioned: 6 Post(s)
Tagged: 0 Thread(s)
That key is selected randomly by the developer(activision, ea, ubisoft, square...) and it is a parameter used when creating a pkg. So for EDAT the key for the third hash is devklic xored with npdrm_omac_key2.

If we are going to recrypt an EDAT we need that key. There are several procedures to obtain it:

- Decrypt the SELF and use RCE to get it. We'll need an idc that locates the call. Very slow, tricky, requires large knowledge but always work.
- Hook the call that opens EDAT. Then we retrieve it on parameter r3. Faster, requires modifying the firmware. Always work
- Brute force it: Decrypt the self and try every combination of 16 sequential bytes on the file. I obtained using this method the key on Buzz and LBP. It faster than RCE but it does not always work (the key could be in other file or obfuscated).
look out for klicensee.py
developer klic is within the .pkg at offset 0x60 or so too
tiefputin2 is offline   Reply With Quote
Likes: (1)