<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>afterguard on Aftermarket.dev</title>
    <link>https://aftermarket.dev/tags/afterguard/</link>
    <description>Recent content in afterguard on Aftermarket.dev</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 21 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aftermarket.dev/tags/afterguard/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>AfterGuard Released to Put a Lock on Old Apps That Have None</title>
      <link>https://aftermarket.dev/afterguard-released-to-put-a-lock-on-old-apps-that-have-none/</link>
      <pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/afterguard-released-to-put-a-lock-on-old-apps-that-have-none/</guid>
      <description>Aftermarket 0.6.0 adds AfterGuard, run as aftermarket guard. It&amp;rsquo;s for the app that was never meant to face anyone: an admin panel from 2014 with no login, an internal API with no rate limit, a debug page someone forgot to switch off.
Rewriting those apps rarely happens. The usual fix is a few lines of nginx config that nobody tests, or an IP allow list that stops working the day someone moves offices.</description>
    </item>
    
    <item>
      <title>Case Study: Putting an Old Admin Panel Behind AfterGuard</title>
      <link>https://aftermarket.dev/case-study-putting-an-old-admin-panel-behind-afterguard/</link>
      <pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/case-study-putting-an-old-admin-panel-behind-afterguard/</guid>
      <description>This case uses the examples/legacy-admin folder from the code repository: a small stand-in for a real old admin panel, and the guard.yaml and fixture that ship in every download archive. The commands and output below come from a real run of the downloaded aftermarket 0.6.0 in front of that panel.
The situation The panel was written years ago for one office. It has no login. It lists and adds users under /admin/, serves a daily CSV under /reports/ that the billing system pulls, and has a debug page nobody remembers adding.</description>
    </item>
    
    <item>
      <title>How AfterGuard Was Tested to Let Nothing Ambiguous Through</title>
      <link>https://aftermarket.dev/how-afterguard-was-tested-to-let-nothing-ambiguous-through/</link>
      <pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/how-afterguard-was-tested-to-let-nothing-ambiguous-through/</guid>
      <description>A security gateway is only as good as its worst gap, so AfterGuard got a written threat model before any code, and every promise in it got a test. Six promises: nothing ambiguous gets through, a denied request never reaches the app, allowed traffic passes byte for byte, limits hold and memory stays bounded, a client can&amp;rsquo;t choose its identity or address, and no secret reaches a log.
Nothing ambiguous This is the one that matters most.</description>
    </item>
    
  </channel>
</rss>
