Post: possible theory on .ff's
12-05-2010, 05:46 PM #1
donny_boy1189
DiRTY HARRY
(adsbygoogle = window.adsbygoogle || []).push({}); I know alot of people here are like f**k you treyarc for encrypting the files (.ff files) in the patch, but have any of you thought that it may just be sony signing them the same way they do with .self's and .eboot's.

Soon graf will release either a payload or info on how to decrypt the game self's and eboot's which will make it possible to create our own debug versions of retail patches, maybe with a little modification or even with none, the same application will decrypt the .ff's for us...



p.s if im talking aload of sh*t feel free to tell me lol.
(adsbygoogle = window.adsbygoogle || []).push({});
12-06-2010, 02:31 AM #11
hunter12
Retired, done with gaming
Originally posted by ihaxgames View Post
I wonder if the .SELF files or eboot.bin files could tell the game how to decrypt and encrypt the Fastfiles, seems plausible?


Sure the functions there, but its not going to be like
"!HERES THE FUNCTION TO DECRYPT, HACK ME HERE!" xD
Basically looking at the .self in a hex editor will be no use.
It's not going to have any text that has to do with the
encrypting/decrypting of the fast files. What everybody is seeing about
the SHA1, LibTomCrypt, MD5, has NOTHING to do with the fast files...
12-06-2010, 02:36 AM #12
ihaxgames
Treasure hunter
Originally posted by hunter12 View Post
Sure the functions there, but its not going to be like
"!HERES THE FUNCTION TO DECRYPT, HACK ME HERE!" xD
Basically looking at the .self in a hex editor will be no use.
It's not going to have any text that has to do with the
encrypting/decrypting of the fast files. What everybody is seeing about
the SHA1, LibTomCrypt, MD5, has NOTHING to do with the fast files...

Regardless, if the system can't do it, the game HAS to
12-07-2010, 05:07 AM #13
jfed
Climbing up the ladder
Originally posted by hunter12 View Post
Sure the functions there, but its not going to be like
"!HERES THE FUNCTION TO DECRYPT, HACK ME HERE!" xD
Basically looking at the .self in a hex editor will be no use.
It's not going to have any text that has to do with the
encrypting/decrypting of the fast files. What everybody is seeing about
the SHA1, LibTomCrypt, MD5, has NOTHING to do with the fast files...


didn't they encrypt the .ff with tiger?? which is extremely hard to break??

Copyright © 2026, NextGenUpdate.
All Rights Reserved.

Gray NextGenUpdate Logo