<?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>Fun With Fuzzing [Day 2]</title>
                            <pubDate>Thu, 23 Jun 2005 16:30:38 -0500</pubDate>
                                        <link>https://www.openrce.org/blog/view/6/Fun_With_Fuzzing_[Day_2]</link>
                                        <author>dyngnosis &lt;email-suppressed@example.com&gt;</author>
                                                    <description> Fuzzer: Day 2&lt;br /&gt;
So Fuzzer-1.1 is great and we've had a lot of fun with it.. Yesterday we played with it and ran it out of the box... but to disover your own 0day you need to take this puppy out of the box and play with it. We also found the found the user manual for Bullet Proof FTP manuals and found an extra set of commands that the server accepts. This is perfect new testing grounds!&lt;br /&gt;
&lt;br /&gt;
[SNIP]&lt;br /&gt;
&lt;br /&gt;
</description>
                    </item>
                <item>
            <title>Fun With Fuzzing [Day 1]</title>
                            <pubDate>Thu, 23 Jun 2005 16:29:33 -0500</pubDate>
                                        <link>https://www.openrce.org/blog/view/5/Fun_With_Fuzzing_[Day_1]</link>
                                        <author>dyngnosis &lt;email-suppressed@example.com&gt;</author>
                                                    <description>Fun with Fuzzing&lt;br /&gt;
We will start with a quick definition of fuzzing and then move directly into the technical stuff.&lt;br /&gt;
&lt;br /&gt;
[SNIP]&lt;br /&gt;
Fuzz testing is a software testing technique. The basic idea is to attach the inputs of a program to a source of random data. If the program fails (for example, by crashing, or by failing in-built code assertions), then there are defects to correct.&lt;br /&gt;
&lt;br /&gt;
The great advantage of fuzz testing is that the test design is extremely simple, and free of preconceptions about system behavior.&lt;br /&gt;
[/SNIP]&lt;br /&gt;
&lt;br /&gt;
So what does that mean? Basically you use a script to automate feeding bad commands to a server and see if it fails. In my case, I</description>
                    </item>
            </channel>
</rss>
