aionskyg
Member
- Joined
- Sep 3, 2012
- Messages
- 132
- Reaction score
- 0
You have been locked up . This is definitely the thing.

Take the following facts speak :
The Warden works: the game client to connect to the server when entering the game ( when logged in ) , the client and server side first negotiate a new session key (128位RC4) for subsequent Warden communications. negotiate encryption process . The focus here is to understand , warden of the data exchanged between the client and the server is encrypted , the key is dynamically generated.
Fraud detection module (Warden.mod) on the server side ( the content is not already fixed size ) . After the establishment of the local Warden Service server using packet AE Warden.mod sent to the game client , this can be done randomness detection mechanism .
Here is part of my content Warden.mod intercepted Today:
seg000: 7AF6211A aKernel32_dll db 'KERNEL32.dll', 0
seg000: 7AF6212A aProcess32first db 'Process32First', 0
seg000: 7AF6214C aIsbadreadptr db 'IsBadReadPtr', 0
seg000: 7AF6216D aModule32first db 'Module32First', 0
seg000: 7AF621A4 aProcess32next db 'Process32Next', 0
seg000: 7AF621A6 aGetmodulehandl db 'GetModuleHandleA', 0
seg000: 7AF621F1 aCreatetoolhelp db 'CreateToolhelp32Snapshot', 0
seg000: 7AF6223A aModule32next db 'Module32Next', 0
seg000: 7AF6224B aClosehandle db 'CloseHandle', 0
seg000: 7AF6225C aLstrcmpia db 'lstrcmpiA', 0
seg000: 7AF6225D aUser32_dll db 'USER32.dll', 0
seg000: 7AF6226F aGetwindowtexta db 'GetWindowTextA', 0
seg000: 7AF622AA aEnumwindows db 'EnumWindows', 0
seg000: 7AF622AB aCharupperbuffa db 'CharUpperBuffA', 0
seg000: 7AF622AF aFindwindowa db 'FindWindowA', 0
Somewhat experienced programmer , Process32First, Process32Next is to analyze the suspicious process , Module32First, Module32Next is to analyze suspicious Dll, EnumWindows, FindWindowA is to analyze suspicious window.
Do not take on Diablo 3 other programs can not check the computer to stall , The Warden since the invention is not so Day parade . Otherwise, the year is not a stick and killed so many people .
Then I hang up the afternoon we went down the program . Briefly analyzed . Process is not hidden , the file header is obvious. Very suitable for testing.
So , if you opened the hook program , in fact, Blizzard has been well aware. As for why not seal , personal task is waiting period.
Take the following facts speak :
The Warden works: the game client to connect to the server when entering the game ( when logged in ) , the client and server side first negotiate a new session key (128位RC4) for subsequent Warden communications. negotiate encryption process . The focus here is to understand , warden of the data exchanged between the client and the server is encrypted , the key is dynamically generated.
Fraud detection module (Warden.mod) on the server side ( the content is not already fixed size ) . After the establishment of the local Warden Service server using packet AE Warden.mod sent to the game client , this can be done randomness detection mechanism .
Here is part of my content Warden.mod intercepted Today:
seg000: 7AF6211A aKernel32_dll db 'KERNEL32.dll', 0
seg000: 7AF6212A aProcess32first db 'Process32First', 0
seg000: 7AF6214C aIsbadreadptr db 'IsBadReadPtr', 0
seg000: 7AF6216D aModule32first db 'Module32First', 0
seg000: 7AF621A4 aProcess32next db 'Process32Next', 0
seg000: 7AF621A6 aGetmodulehandl db 'GetModuleHandleA', 0
seg000: 7AF621F1 aCreatetoolhelp db 'CreateToolhelp32Snapshot', 0
seg000: 7AF6223A aModule32next db 'Module32Next', 0
seg000: 7AF6224B aClosehandle db 'CloseHandle', 0
seg000: 7AF6225C aLstrcmpia db 'lstrcmpiA', 0
seg000: 7AF6225D aUser32_dll db 'USER32.dll', 0
seg000: 7AF6226F aGetwindowtexta db 'GetWindowTextA', 0
seg000: 7AF622AA aEnumwindows db 'EnumWindows', 0
seg000: 7AF622AB aCharupperbuffa db 'CharUpperBuffA', 0
seg000: 7AF622AF aFindwindowa db 'FindWindowA', 0
Somewhat experienced programmer , Process32First, Process32Next is to analyze the suspicious process , Module32First, Module32Next is to analyze suspicious Dll, EnumWindows, FindWindowA is to analyze suspicious window.
Do not take on Diablo 3 other programs can not check the computer to stall , The Warden since the invention is not so Day parade . Otherwise, the year is not a stick and killed so many people .
Then I hang up the afternoon we went down the program . Briefly analyzed . Process is not hidden , the file header is obvious. Very suitable for testing.
So , if you opened the hook program , in fact, Blizzard has been well aware. As for why not seal , personal task is waiting period.






