<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Conferences on heapspray.io - a plethora of infosec garbage</title>
    <link>https://heapspray.io/categories/conferences/</link>
    <description>Recent content in Conferences on heapspray.io - a plethora of infosec garbage</description>
    <generator>Hugo -- 0.152.2</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 02 Oct 2010 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://heapspray.io/categories/conferences/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Brucon 2010: a recap</title>
      <link>https://heapspray.io/posts/brucon-2010-a-recap/</link>
      <pubDate>Sat, 02 Oct 2010 00:00:00 +0000</pubDate>
      <guid>https://heapspray.io/posts/brucon-2010-a-recap/</guid>
      <description>&lt;p&gt;I was at Brucon 2010 last week, and it was a &lt;em&gt;blast&lt;/em&gt;!&lt;/p&gt;
&lt;p&gt;The ambiance at the con was very much reminiscent of Defcon&amp;rsquo;s: people
talking passionately about security in a relaxed, geek-and-caffeine-rich
environment.&lt;/p&gt;
&lt;p&gt;In the past, when attending infosec cons I tend to go to all the talks
&amp;ndash; this time, I decided to go to as many workshops as possible. I must
say, I was not disappointed at all &amp;ndash; while talks are often absolutely
fascinating and wildly entertaining,  workshops provide a chance to
understand something at a much deeper level and allow you to test your
knowledge of the topic; it also allows the speaker to tune her content
to the audience in a much more interactive manner, providing more, or
less, background information according to the crowd&amp;rsquo;s grasp of the
subject. For instance, during the malicious PDF analysis workshop,
Didier Stevens provided an overview of the PDF structure and started
working through his samples, but quickly started skipping through
examples he thought were obvious and allotting more time to the &amp;lsquo;juicy
bits&amp;rsquo;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
