* or The faster way is to locate a Static Pointer that will show you the location of the DMA address. A simple Code Cave will allow you to copy the value of the DMA to a static address and read the value. * A redirection of ASM code to a new location where there is more space to add additional code or to modify the string without PB detecting the changes.ġ11112 mov eax etc etc original next ASM lineĥ5555 je short rendDX9.99999 Original Lineĥ5512 Return from cave to next ASM line * A section of the CPU that stores values before execution * It's a peice of ASM code that stores the location of the DMA address in a register. * Punk Buster, an application that checks for changes to the BF2 game in an attempt to prevent cheating. * A BASE address is the memory location where an application or DLL starts. * In Windows, click on START / RUN / CALC The OFFSET is how many bytes from the start the section of code of interest is located. * You can discover the code yourself and subtract the DLLbase to get the offset * There are tools on this forum that will display the info * GameHack will list it under the loaded modules view * OlleyDbg will list it under the Executables view * Enter your values "DLLbase + Offset = Target Address * Search the forums for many posts that give the offsets #IS WINJECT DETECTED CODE# * Go read up on how PB works, you'll come up with many ways.
There is also a link above that takes you to a Tut on how to do it in the most simple way. * PB has a number of tricks, the most common being doing an MD5 hash of a section of static memory. If any changes occure to this section the MD5 checksum will be invalid and PB will know that changes have been made. * MD5 (Message-Digest algorithm 5) is a widely-used cryptographic hash function with a 128-bit hash value. * Yes, it's simply a question of Time and CPU power.
There has also been work done using Rainbow tables to create a database of many encrytion standard hashes.
0 kommentar(er)
