<?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>Network-Security on Caleb Garber</title>
    <link>https://calebgarber.com/tags/network-security/</link>
    <description>Recent content in Network-Security on Caleb Garber</description>
    <generator>Hugo -- 0.165.0</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 03 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://calebgarber.com/tags/network-security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>What my swarm encrypts is a kernel question</title>
      <link>https://calebgarber.com/posts/docker-overlay-encryption-what-my-swarm-encrypts/</link>
      <pubDate>Tue, 03 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://calebgarber.com/posts/docker-overlay-encryption-what-my-swarm-encrypts/</guid>
      <description>Docker Engine 29.9.0 fixed a reference counting error that could remove an in-use IPsec tunnel from an encrypted overlay network and let VXLAN traffic to some peers go out in cleartext. The fix carries no CVE, so the only way I found it was the release notes. What I check now is the kernel state on each node, not the encrypted flag in the network options.</description>
    </item>
  </channel>
</rss>
