dELTA
October 16th, 2006, 14:10
Thanks for the French lesson fr33ke, I've corrected my post.
Nice to see you interested in the topic anyway! When you are asking for suggestions regarding the output form of your potential tool, are you referring to a disassembler that will mark up all possibly overlapping opcodes, like the one LLXX is talking about, or a code analyzer/rebuilder/deobfuscator that I'm talking about?
First of all, starting out a project like this with trying to make up a fancy GUI will often run the risk of killing off your interest before you even get really started with the good stuff.

I'd say dive into the theoretical stuff first, and worry about presenting it later, it's the program logic of such an operation that we all want, and in the worst case we'll live with any crappy GUI to get it.
But actually, my main idea does not even require a GUI at all!

What I'm picturing is a deobfuscator that analyzes code, and then produces deobfuscated/non-overlapping code as output. This code (a new version of the inputted SWF file) could then be viewed in any Flash disassembler of people's choice, thus leaving the GUI question to themselves, and the fun stuff to you!

The tool would basically be a generic cleaner of overlapping-opcode protections (and possible also other such easily identifyable/cleanable tricks, I'm sure some of the other "anti debug" tricks have this property too). Such a tool would quickly become a must-have for all Flash reversers, something that they'd always apply as a first layer of deprotection, before proceeding with their other tools!
If you don't understand my simple thought-out design for the deobfuscation process from my brief explanation above, please ask more and I'll explain further!
Also, come on people, there's still room for a few more names in the history of Flash reversing glory, join in!
