<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Arduino on Insinuator.net - Bold Statements</title>
    <link>https://insinuator.net/tags/arduino/</link>
    <description>Recent content in Arduino on Insinuator.net - Bold Statements</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 18 May 2016 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://insinuator.net/tags/arduino/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Introduction of a new hardware guy</title>
      <link>https://insinuator.net/2016/05/introduction-of-a-new-hardware-guy/</link>
      <pubDate>Wed, 18 May 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/05/introduction-of-a-new-hardware-guy/</guid>
      <description>&lt;p&gt;Hi folks!&lt;/p&gt;&#xA;&lt;p&gt;We couldn’t be more proud to welcome such a predestined #1 hardware hacking victim, than &lt;strong&gt;VICTor&lt;/strong&gt; is!&lt;br&gt;&#xA;Before Brian and I gave a lecture on hardware hacking last week at &lt;a href=&#34;https://www.mosbach.dhbw.de&#34;&gt;DHBW Mosbach&lt;/a&gt;, we felt, that we needed a custom victim which is fully documented and provides a good “hackability” to the students.&lt;br&gt;&#xA;Surely we could also have used some cheap $wifi_ap, but here’s the thing: Would you really want to use a device which you don’t really know? Mostly, there’s a massive lack of documentation regarding the SoCs used…not to mention the unavailability of schematics and layouts.&lt;br&gt;&#xA;As we wanted to teach students the basics of hardware hacking effectively, we decided to create something by ourselves.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
