<?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>Security on Intent</title>
    <link>https://intent.me/en-us/categories/security/</link>
    <description>Recent content in Security on Intent</description>
    <generator>Hugo -- 0.155.1</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 28 May 2026 18:59:25 +0800</lastBuildDate>
    <atom:link href="https://intent.me/en-us/categories/security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>IIoT Ingress Postmortem: Troubleshooting EMQX 5.8 Under Podman Rootless</title>
      <link>https://intent.me/en-us/blog/tech/iiot-emqx-rootless-deployment-postmortem/</link>
      <pubDate>Thu, 28 May 2026 18:59:25 +0800</pubDate>
      <guid>https://intent.me/en-us/blog/tech/iiot-emqx-rootless-deployment-postmortem/</guid>
      <description>A postmortem of an IIoT ingress deployment failure: under Podman Rootless, EMQX 5.8 exposed unstable Erlang IPC, HOCON schema validation failures, a blocked security-group port, and M2M requests rejected by CSRF middleware. This post covers the confirmed causes, fixes, and validation path.</description>
    </item>
    <item>
      <title>JWT Dual-Token Hardening Postmortem: From Stateless Refresh to Revocable Redis Sessions</title>
      <link>https://intent.me/en-us/blog/tech/jwt-at-rt-redis-hardening-postmortem/</link>
      <pubDate>Mon, 23 Mar 2026 10:00:00 +0800</pubDate>
      <guid>https://intent.me/en-us/blog/tech/jwt-at-rt-redis-hardening-postmortem/</guid>
      <description>A security hardening postmortem for JWT AT/RT architecture: treating Redis reservation as completed and implementing RT rotation, replay detection, and revocable sessions.</description>
    </item>
    <item>
      <title>HTTPS Upgrade Triggered 403: A Deep Postmortem from Security Middleware to Container Isolation</title>
      <link>https://intent.me/en-us/blog/tech/https-upgrade-403-postmortem/</link>
      <pubDate>Tue, 17 Mar 2026 12:00:00 +0800</pubDate>
      <guid>https://intent.me/en-us/blog/tech/https-upgrade-403-postmortem/</guid>
      <description>A postmortem on a persistent 403 after HTTPS migration, traced to both missing CSRF allowlist updates and Podman Rootless image namespace isolation.</description>
    </item>
  </channel>
</rss>
