<?xml version="1.0"?>
<rss version="2.0">
    <channel>
        <title>OpenRCE: Blog</title>
        <link>http://www.openrce.org/rss/feeds/blog</link>
        <description>OpenRCE: The Open Reverse Code Engineering Community</description>
                <item>
            <title>What do IDA pro and fuzzing have to do with one another?</title>
                            <pubDate>Wed, 28 Mar 2007 15:06:45 -0500</pubDate>
                                        <link>https://www.openrce.org/blog/view/676/What_do_IDA_pro_and_fuzzing_have_to_do_with_one_another?</link>
                                        <author>camill8 &lt;email-suppressed@example.com&gt;</author>
                                                    <description>Why does IDA pro exist?&amp;nbsp;&amp;nbsp;Simply stated, because humans can look at assembly and make more sense out of it better than a program can decompile it.&amp;nbsp;&amp;nbsp;And the prevalence of IDA pro means people think this isn't going to change anytime soon.&amp;nbsp;&amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
So, what does this have to do with fuzzing?&amp;nbsp;&amp;nbsp;Well, a lot of time has been spent recently discussing how to make fuzzers &amp;quot;smarter&amp;quot;.&amp;nbsp;&amp;nbsp;By this people generally mean either 1) more protocol aware or 2) cabable of incorporating runtime information into it's decisions, i.e. by looking at code coverage.&amp;nbsp;&amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
The fundamental question comes, like in IDA pro, as to whether this is a job more suited to a human or a program.&amp;nbsp;&amp;nbsp;I'm starting to lean toward the former - mostly because I've seen how hard it is to do the latter!&amp;nbsp;&amp;nbsp;If you start to believe this is always going to be a human endevor, it makes sense to start building tools which make it easier for a human to interact and change the way a fuzzer behaves, much like IDA makes it easier for a human to understand a disassembled program.&amp;nbsp;&amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
To this end, I've started writing a program VisFuzz which helps an analyst describe a protocol to a &amp;quot;fuzzer&amp;quot; in an intuitive way.&amp;nbsp;&amp;nbsp;Then the fuzzer can take this information and fuzz the target.&amp;nbsp;&amp;nbsp;The important fact being the focus is not on &amp;quot;fuzzing&amp;quot; but the interaction between the user and the fuzzer.&lt;br /&gt;
</description>
                    </item>
            </channel>
</rss>
