Post: [MW2]► 1.12 Retail Released
Options
02-17-2011, 12:22 AM
#1
Cain
Tutorial Team Like A Boss
:hitman: Sony, we're after you.
Ok, i'll try to explain that a little better.
I searched for BLES00683, and it would not find at all. It was not retail, and it was not debug. Generally this means they are in the process of being uploaded and set for Sony's servers, so expect a patch for TUESDAY so enjoy your lobbies until then.
Better?
The following user thanked Cain for this useful post:
02-17-2011, 02:31 PM
#20
jfed
Climbing up the ladder
about time mw2 got destroyed because of all the little kids hacking it was better when you need 2 ps3's.
---------- Post added at 09:31 AM ---------- Previous post was at 09:29 AM ----------
well is the new patch_mp.ff encrypted? or do we just have to keep the parts at the exact same size?
---------- Post added at 09:31 AM ---------- Previous post was at 09:29 AM ----------
Originally posted by hunter12
you can't decrypt the EBOOT unless you have the NPDRM keys.
To everyone else, the security is not in the patch_mp.ff. editing it will just result in a black screen changing one byte will result in a black screen. basically if you cant decrypt the eboot, you wont be running modded "patches"
bypassing the 1.12 update will be pointless to because the playlist version is stored on the server AND in the executable. so if you bypass the only people you will be playing with is other people who have bypassed. just like COD4
To everyone else, the security is not in the patch_mp.ff. editing it will just result in a black screen changing one byte will result in a black screen. basically if you cant decrypt the eboot, you wont be running modded "patches"
bypassing the 1.12 update will be pointless to because the playlist version is stored on the server AND in the executable. so if you bypass the only people you will be playing with is other people who have bypassed. just like COD4
well is the new patch_mp.ff encrypted? or do we just have to keep the parts at the exact same size?
The following 2 users say thank you to jfed for this useful post:
02-17-2011, 03:22 PM
#22
tylerallmighty
Human After All
The following user thanked tylerallmighty for this useful post:
02-24-2011, 12:00 PM
#25
IDontbreak
Cake is a lie
Originally posted by hunter12
you can't decrypt the EBOOT unless you have the NPDRM keys.
To everyone else, the security is not in the patch_mp.ff. editing it will just result in a black screen changing one byte will result in a black screen. basically if you cant decrypt the eboot, you wont be running modded "patches"
bypassing the 1.12 update will be pointless to because the playlist version is stored on the server AND in the executable. so if you bypass the only people you will be playing with is other people who have bypassed. just like COD4
To everyone else, the security is not in the patch_mp.ff. editing it will just result in a black screen changing one byte will result in a black screen. basically if you cant decrypt the eboot, you wont be running modded "patches"
bypassing the 1.12 update will be pointless to because the playlist version is stored on the server AND in the executable. so if you bypass the only people you will be playing with is other people who have bypassed. just like COD4
Does the default_mp.self have any security in it?
For a fact, the updated one is going to be bigger in size.
02-24-2011, 12:17 PM
#26
DEREKTROTTER
You're Goddamn Right
Originally posted by IDontbreak
Does the default_mp.self have any security in it?
For a fact, the updated one is going to be bigger in size.
For a fact, the updated one is going to be bigger in size.
i found this in the .self, not sure if this is the protection though:
getSerializedSize.......getHash.set.....operator[]......calculateHash
deserialize.....
deserialize.....
getUserKey......
serialize.......
serialize.......
Þ.¾ïÞ.¾ïÞ.¾ïÞ.¾ï........
getLicenseKey...
serialize.......
serialize.......
serialize.......
deserialize.....
deserialize.....
deserialize.....
serialize.......
serialize.......
Then this, same as in Black ops .SELF ~ not sure if this was put into all COD's though, like a server check
14bdHashTiger192........
warn/...
hashtiger192....
c:/trees/build-iw4-ps3-2/iw4/code_source/DemonWare/bdCore/bdCrypto/bdHashTiger192.cpp...
Tiger hash only requires result buffer of 24 bytes. Remainder of buffer will not be used.......tiger...err/....Unable to create tiger hash of less than 24 bytes in length!....Unable to create hash...Unable to register hash
The following user thanked DEREKTROTTER for this useful post:
not always/facepalm
Copyright © 2026, NextGenUpdate.
All Rights Reserved.
