Reverse engineering guide for beginners: Methodology and tools
1–10 of 70 posts
Re: Reverse engineering guide for beginners: Methodology and tools
#2Where RE is reverse engineering, as opposed to say, regular expressions.
Re: Reverse engineering guide for beginners: Methodology and tools
#3Where RE is reverse engineering, as opposed to say, regular expressions.
Looks like the title has been amended
Re: Reverse engineering guide for beginners: Methodology and tools
#4Evan's debugger is nice for Olly fans
Re: Reverse engineering guide for beginners: Methodology and tools
#5Blank page without javascript. Bye.
Re: Reverse engineering guide for beginners: Methodology and tools
#6Where RE is reverse engineering, as opposed to say, regular expressions.
Nobody in tech thinks RE stands for regular expression...
Re: Reverse engineering guide for beginners: Methodology and tools
#7Where RE is reverse engineering, as opposed to say, regular expressions.
Use regex for regular expressions (some people even use regexpr)
Re: Reverse engineering guide for beginners: Methodology and tools
#8I'd love to know more about disassembly. I've recently had more and more reason to go deeper into applications I'm running as dependencies. A few issues I've found and fixed just by using strace to get an idea of the system calls.
There was one thing in particular where I knew there was a jump somewhere (if some_length I wanted something that could give me a few seconds worth of samples of where the instruction register was spending its time as a starting point, but couldn't find any such tool (linux).
Within my control:
- giving input files to explicitly set unique numbers to watch out for
- giving inputs that would generate bad output numbers only in the bad code path
- giving inputs to force a load of jumps down the bad or good code paths
Re: Reverse engineering guide for beginners: Methodology and tools
#9After brushing up on this, if you're looking for something "fun" to work through, the NSA's 2016 Codebreaker challenge is good, granted you have a .edu email address (only US .edu too, unfortunately).
https://codebreaker.ltsnet.net/challenge
I think they're going to be keeping the 2016 version up for a while longer. They generally start a new one in September each year.