![]() Web
: http://kickme.to/mxbnet CuteFTP 5.0 XP - Build 50.6.10.2
Type : FTP Client Crack : Cute FTP does a OnLine check of S/N entered .. and validates it.I was wondering how it is done.To find it use a proxy server ... as it shows every http request.And enter S/N in Cute FTP.Proxy server reveals what this baby is doing with our S/N ... with which server it is checking.Following are its result ..
POST http://dbregistration.cuteftp.com/what_xou_like.reg HTTP/1.0
CUTERG0100046B657931000E413232323232323232323232323200046B65793200404E4D4D4F38574E So our S/N is validated by "dbregistration.cuteftp.com" visit this server by your browser and you can see a interesting string showed in your browser ... CUTERG010007636F6D6D616E64000B696E76616C696464617461 - This means "d invaliddata" So this is how comunication is taking place ... we are not doing our stuff ... here just for info. This baby can easily be stoped from verifying our S/N [OnLine check] by just changing the name of server to what ever you like ..."xbregistration.cuteftp.com" using a hex editor. But there is also a nasty CRC Check and Memory check sum ... going on in seperate thread ... CRC Check - Memory Check Sum : This baby is doing these checks in a seperate thread .. Memory check sum is done using API ... MAPVIEWOFFILENAME ...GETMODULEFILENAMEA ... We can't put BPX on any address as it corrupts its memory and Consistency check will trace out it .. so use hardware break point - BPMB cs:xxxxxx X.Most funnniest part is that we can't patch it as CALL to this routine will depend upon its virginity.If we patch it CALL to this routine will point to some address and result is page fault.Never mind outer call can be patched. BPX MAPVIEWOFFILE ... trace back we will end here ...
CALL [EBP-18] Inside this call ..
004773A7 MOV EAX,01 Put a BPMB in side this routine and you will break where every it is called.Main outside calls calling this routine are ..
0044445E CALL [00556E1C] 00477BD0 JMP 00477BDA = EB 08 OFFSET = 77BD0 00477B9A JMP 00477BAA = EB 0E OFFSET = 77B9A S/N .. Now go offline and register this program with this S/N .....
S/N = A2222222222222 It will tell that S/N seems to be ok but not verified ... See "About Box".A quick view with Win32DASM shows that CALL 00404110 is the main sucker behind this ....Inside this CALL we will alter flag clearing part ..
004043FE XOR EAX,EAX = 33 C0 Now we have finished ... it is working fine and "About Box" shows it is licensed to me ...
|