
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Quo&#39;s Blog</title>
      <link>https://quos-blog.vercel.app/blog</link>
      <description>Personal blog and portfolio of Quo - sharing technical blogs and projects</description>
      <language>en-au</language>
      <managingEditor>undefined (Quo)</managingEditor>
      <webMaster>undefined (Quo)</webMaster>
      <lastBuildDate>Wed, 27 Nov 2019 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://quos-blog.vercel.app/tags/ringzer0/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://quos-blog.vercel.app/blog/crackme-challenge-3</guid>
    <title>Crackme Challenge #3 - Ringzer0 Crack Me 1</title>
    <link>https://quos-blog.vercel.app/blog/crackme-challenge-3</link>
    <description>Walkthrough of Ringzer0 Crack Me 1 challenge by Mr.Un1k0d3r, demonstrating PE resource analysis and dynamic reverse engineering techniques.</description>
    <pubDate>Wed, 27 Nov 2019 00:00:00 GMT</pubDate>
    <author>undefined (Quo)</author>
    <category>crackme</category><category>reverse-engineering</category><category>ringzer0</category><category>ollydbg</category><category>ida</category><category>peview</category><category>resources</category>
  </item>

  <item>
    <guid>https://quos-blog.vercel.app/blog/crackme-challenge-4-5</guid>
    <title>Crackme Challenge #4 &amp; #5 - Windows x86 Reversing &amp; Windows API</title>
    <link>https://quos-blog.vercel.app/blog/crackme-challenge-4-5</link>
    <description>Walkthrough of two Ringzer0 challenges: &quot;Windows x86 reversing is cool&quot; and &quot;Windows API for the win&quot;, demonstrating reverse engineering techniques on Windows executables.</description>
    <pubDate>Sun, 01 Dec 2019 00:00:00 GMT</pubDate>
    <author>undefined (Quo)</author>
    <category>crackme</category><category>reverse-engineering</category><category>ringzer0</category><category>ollydbg</category><category>ida</category><category>x86</category><category>windows-api</category>
  </item>

    </channel>
  </rss>
