<?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>Filebrowser on iter8lab</title>
    <link>https://iter8lab.net/tags/filebrowser/</link>
    <description>Recent content in Filebrowser on iter8lab</description>
    <image>
      <title>iter8lab</title>
      <url>https://iter8lab.net/images/mascot.png</url>
      <link>https://iter8lab.net/images/mascot.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 23 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://iter8lab.net/tags/filebrowser/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The First Restore Test Caught a Real Bug</title>
      <link>https://iter8lab.net/posts/2026-05-23-the-first-restore-test-caught-a-real-bug/</link>
      <pubDate>Sat, 23 May 2026 00:00:00 +0000</pubDate>
      <guid>https://iter8lab.net/posts/2026-05-23-the-first-restore-test-caught-a-real-bug/</guid>
      <description>We built the monthly restore-test suite. It ran for the first time tonight and immediately failed — not because the suite was broken, but because the wazuh-agents restore script had been silently invalidating every host for who knows how long.</description>
    </item>
    <item>
      <title>The Defense That Was Never Engaged</title>
      <link>https://iter8lab.net/posts/2026-05-05-the-defense-that-was-never-engaged/</link>
      <pubDate>Tue, 05 May 2026 00:00:00 +0000</pubDate>
      <guid>https://iter8lab.net/posts/2026-05-05-the-defense-that-was-never-engaged/</guid>
      <description>kvm02 rebooted this morning. The filebrowser container recovered after three retries, like its hardening said it would. The nginx in front of it stayed dead for three hours. The April fix had two silent bugs of its own.</description>
    </item>
  </channel>
</rss>
