![]() ![]() Remember when i said that we were gonna break when windows passed our entered string to the VB dll?) Step 3 : Leave softice with control-d. In this case it will be used to copy the buffer with the text we entered to the memory space of the VB dll. (Intermezzo : What is hmemcpy? Windows uses hmemcpy alot in operations concerning strings. In softice enter ‘bpx hmemcpy’ to place a breakpoint on the hmemcpy function of the kernel. So therefore i will split the cracking process in smaller chunks : Step 1 : Run The Collector right at startup it will ask you for a serial # Step 2 : Enter a dummy serial like ‘9876543210’. ![]() Continue reading forĭLL : uses VB3 dll <************** VB3.DLL I find it easier to explain things in steps. Setting a single breakpoint at the right place. It would reduce VB cracking to a boring job of Wouldnt it be great if we knew where, in the dll, 2 strings get compared? And that turns out toīe the case, as you will see if you finish reading this document.ĭoes the little lamp already begin to glow in your head ? –) Inside the dll where two strings can be compared. So therefore a good guess is that there will be only 1 (or 2) place(s) The VB dll made 10 different functions you could use in order to compareĢ strings? No, of course not. What does this mean? It means that there is a big disadventage to They make calls to a library with standard functions. We are dealing with exe’s that dont have code themselves but instead Before i start bombing you with asm listings lets take a moment to ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |