(adsbygoogle = window.adsbygoogle || []).push({}); I was snooping through the retail t5mp_ps3f.self file today and noticed a load of command strings saying

    Size of data to encrypt is too large

    yarrow rsa_encrypt_key %sCan't encrypt uninitialized public key

    Unable to create private key %s.Cannot reinitialize key

Like everyone has said the public key is hidden amongst the game files.

Note: If I do get onto something big, I won't be posting on the NGU threads just in case it does get noted by Treyarch.

Here are some pictures!

Pics:
You must login or register to view this content.
Please note in the picture the "MD5 hash only requires result buffer of 16 bytes"
So the public key cannot be bigger then 16 bytes nor can the private key. But lets not talk about the private key as for that will be the hardest to obtain.

And also please note that this isn't a "debug" t5mp_ps3f.self file. I put Black Ops into my JB PS3 then opened up "Open Manager" and then backed up my game. After that was completed I extracted every single game file via FTP server.

Which was about 18GBs. So there you guys go, a retail .self file

Extra Info: I just found and discovered some new info... mostly about "Tiger"..


Tiger the key's for the RSA encryption for Black Ops is 16 bytes/128 bits. So Tiger would be "Truncated version Tiger/128" But its obvious to say that its Tiger with MD5 hash marks, as it refers to in the (which would be "Tiger2") t5mp_ps3f.self file... which wasn't encrypted in the retail .self?? Treyarch's challenge maybe... but the majority of the file is encrypted.

I also noted another part of the file where it mention Tiger/192(192 bit) or 24 bytes. Which I would almost guarantee is used to hash the private key. But until we decided what hash goes with what, we really can't move further forward.

Nice finds, I hope you can do something good with them.

I'm sure I can

Its just a matter of if and when.

---------- Post added at 04:19 PM ---------- Previous post was at 03:31 PM ----------



Its already been cracked on 360

And it cannot be ported to PS3 since we haven't decrypted the patch nor can we encrypted it yet... so good luck with that.

This is probably just a string that calls the private/public keys. I dont think you should be looking in a debug t5mp, i mean even if u get it working, how are you goin to transfer it onto a 3.50 ps3? But ya good luck!

Depends... But what would make the public key change... if its debug or retail... and by the way. Its a retail .self :p just saying.

Nothing new here...

Download the .pkg debug on ps3news, make_package_npdrm.exe -x command, open the t5mp_ps3f.self on HxD and there you go :whistle:

People are tryin to figure out the private key
But y are'nt there people trying to figure away around it

Like I doubt that TheUnkn0wn has figured out the private key. I think that he has figured away a round it

So y don't we try what TheUkn0wn has done (maybe he has got the code )

I think TheUnkn0wn can't decrypt the .ff files at the moment i write this message but he work on it try to figure it out

Well TheUkn0wn has shown that he has hacked the xp so that means that he has did something maybe he has decrypted the encrypted it without the private key

I dnt knw but the guy has got Skill a hacking/Moding

---------- Post added at 09:47 PM ---------- Previous post was at 09:46 PM ----------

Well TheUkn0wn has shown that he has hacked the xp so that means that he has did something maybe he has decrypted the encrypted it without the private key

I dnt knw but the guy has got Skill a hacking/Moding

... This is just a retail .self file.
What is special about the debug .self file might I ask?