Quote:
|
Originally Posted by TQN
This method of hacnho can only applied with a small and simple packed exe. OllyDbg will fail when tracing with a large, complex exe. For example, I download FSG 1.0 from this site (ExeTools), pack the Stud_PE and trace with OllyDbg. Failed to find OEP.
|
Your post intrigued me as I had not experimented much beyond "simple" apps with FSG.
I downloaded Stud_PE 1.8.0 (file size 663,552 bytes), I assume that was your target?
Then compressed it with FSG 1.0 resulting in a packed exe 288,864 bytes in size.
I loaded it into Olly (1.10s2) and let it trace bytewise to entry, stopping at OEP.
After a long time, in the order of 10 minutes or so, it arrived on the OEP.
---> OEP 0039F14 <55 PUSH EBP>
(Note: Same as reported by PEiD)
Dumped with OllyDump 2.21.108, no rebuild.
Fixed Imps with ImpRec, all valid.
Ended with an ugly, but fully functional Unpacked Stud_PE.exe (983,040 bytes)
Just for kicks I FSG'd several misc apps (MASM & VC4-6)
Ran them all thru Olly in the way described above. And resolved all OEP's correctly.
I did hit a few snags after OEP on a few of the test apps,
(Note: due to 1-year old daughter clearing off desk rapidly at this moment I must be brief)
One app, PEid did not report the correct OEP with generic OEP finder.
One app, dumped ok, but could not rebuild imports with ImpRec even though all valid.
(haven't had time to look into why)
I to am interested in finding the manual way to OEP and will continue testing
when time allows.
-bg