|
hmm let me be the first to say this crack is shit heh
basically the code loads up, then virtualalloc's memory blocks
(with NO handling for failure... just a lame 'memory error' messagebox), then reads the file data into them
the dumped data is not dvd data as chron states, its basically
a dump of memory (virtualalloc hooked?) which they then reload again
needless to say if the virtualalloc fails (as they try and get the address on the same base as the dumped it from... which simply wont work on some pc's.. dll's might be loaded there etc..) then the entire thing will crash when that code is called...
the filenames of the files are the virtual memory address they were dumped from
and theres a lot of 00's which the cracker could have trimmed making the crack smaller, as virtualalloc'd memory is automatically zerofilled to begin with...
oh yeh and the data has the users environment dumped.. administrator... computer name flf, does noone even bother to crack properly anymore?
simple loader, injection approach... flawed
innovative... hardly, did you actually analyse it joe?.. its dumped vm fragments amongst other things...
__________________
bleh
DO NOT PM me with questions, leave that in the forums...ESPECIALLY if i dont know you...
Last edited by TippeX; 06-09-2006 at 10:23.
|