<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Automation on Insinuator.net - Bold Statements</title>
    <link>https://insinuator.net/tags/automation/</link>
    <description>Recent content in Automation on Insinuator.net - Bold Statements</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 17 Aug 2018 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://insinuator.net/tags/automation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>IPython Support for Binary Ninja</title>
      <link>https://insinuator.net/2018/08/ipython-support-for-binary-ninja/</link>
      <pubDate>Fri, 17 Aug 2018 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2018/08/ipython-support-for-binary-ninja/</guid>
      <description>&lt;p&gt;This blogpost is about the release of a plugin for Binary Ninja that allows you to run a Python Kernel inside the Binary Ninja GUI environment to which you can attach a Jupyer (QT) console, formerly known as IPython shell. The first section is about why this is useful, the second is about some issues I encountered and how to solve them, and the third contains everything you need to know to set it up.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Virtualized Training Environment with Ansible</title>
      <link>https://insinuator.net/2018/02/virtualized-training-environment-with-ansible/</link>
      <pubDate>Fri, 02 Feb 2018 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2018/02/virtualized-training-environment-with-ansible/</guid>
      <description>&lt;p&gt;As Kai and I will be holding a &lt;a href=&#34;https://troopers.de/troopers18/trainings/tr18-automation-with-ansible/&#34;&gt;TROOPERS workshop on automation with ansible&lt;/a&gt;, we needed a setup for the attendees to use &lt;a href=&#34;https://www.ansible.com/&#34;&gt;ansible&lt;/a&gt; against virtual machines we set up with the necessary environment. The idea was, that every attendee has their own VMs to run ansible against, ideally including one to run ansible from, as we want to avoid setup or version incompatibilities if they set up their own ansible environment on their laptop.  Also they should only be able to talk to their own machines, thus avoiding conflicts because of accidental usage of wrong IPs or host names but also simplify the setup for the users.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
