How to study behaviour in the code, continued inlining using a pointerġ7. More difficult schemes and an introduction to inline patchingġ5. The use of API's in software, avoiding doublechecking tricksġ4. Guiding a program by multiple patching.ġ3. Intermediate patching using Olly's "pane window"ġ2. Continued reversing techniques in VB, use of decompilers and a basic anti-anti-trickġ1. Explaining the Visual Basic concept, introduction to SmartCheck and configurationġ0. Debugging with W32Dasm, RVA, VA and offset, using LordPE as a hexeditorĠ9. Intermediate level patching, Kanal in PEiDĠ8. "The plain stupid patching method", searching for textstringsĠ7. Comparing on changes in cond jumps, animate over/in, breakpointsĠ6. Olly + assembler + patching a basic reversemeĠ5. this is typically a classic case of "if you even have to ask, then it's not for you." If you have some very rare and odd friends willing to show you the ropes, if you're a terrific self-starter with lots of discipline and time to waste, or if you've already got a degree in computer science then the idea might be worth investigating, but in most cases it's just a pipe-dream that people should shelve.Ġ1. Work your way up to the hard stuff, and hopefully you'll meet some hip and in-the-know people to give you some specific advice.īut. Next step would be to just jump in the shallow end of the pool and actually do it. Then there's the various common forms of crypto: AES and RSA being used frequently. Then explore common methods for calculating checksums/CRCs. hex/ASCII, API calls, x86 Assembly, and bitwise operations/logic (like what happens when you're XORing by 1, ANDing by 0, etc.) for starters. There are plenty of non-protection specific things to learn: How to use a debugger, binary vs.
0 Comments
Leave a Reply. |