<?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>Disclosure on Ethan Thomason</title>
    <link>https://ethomason.com/tags/disclosure/</link>
    <description>Recent content in Disclosure on Ethan Thomason</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 27 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://ethomason.com/tags/disclosure/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Restoring Trust: A Code-Execution Story in Ignition Gateway Backups</title>
      <link>https://ethomason.com/posts/restoring-trust-ignition-gateway-backups/</link>
      <pubDate>Thu, 27 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://ethomason.com/posts/restoring-trust-ignition-gateway-backups/</guid>
      <description>&lt;h1 id=&#34;restoring-trust-a-code-execution-story-in-ignition-gateway-backups&#34;&gt;Restoring Trust: A Code-Execution Story in Ignition Gateway Backups&lt;/h1&gt;
&lt;p&gt;I spend most of my time inside Inductive Automation&amp;rsquo;s Ignition platform. Years of integration work will do that — you get to know a system&amp;rsquo;s habits, the places it trusts input a little too readily, the seams where convenience and security pull in opposite directions. Lately I&amp;rsquo;ve been pointing that familiarity in a different direction: instead of building on Ignition, I&amp;rsquo;ve been probing it. This is the story of one of those probes, and of a disclosure process that worked the way it&amp;rsquo;s supposed to.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
