<?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>NTP on Aperture Zone</title>
    <link>https://aperturezone.com/tags/ntp/</link>
    <description>Recent content in NTP on Aperture Zone</description>
    <image>
      <url>https://aperturezone.com/logo.webp</url>
      <link>https://aperturezone.com/logo.webp</link>
    </image>
    <generator>Hugo -- gohugo.io</generator>
    <language>fr-fr</language>
    <lastBuildDate>Sun, 05 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aperturezone.com/tags/ntp/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How a 2012 NTP GPO Will Cause Kerberos to Fail in 2026</title>
      <link>https://aperturezone.com/posts/ntp/</link>
      <pubDate>Sun, 05 Jul 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/ntp/</guid>
      <description>&lt;p&gt;A time synchronization GPO, pushed to &lt;strong&gt;all&lt;/strong&gt; my servers back in the Windows Server 2012 days to work around issues/quirks with &lt;code&gt;w32time&lt;/code&gt; at the time, forced each machine to query an NTP Chrony server directly, bypassing Active Directory’s native time hierarchy. This workaround survived two migrations (2012 → 2016 → 2022) without ever causing any problems. But it was &lt;strong&gt;never&lt;/strong&gt; really sound. The Kerberos hardening in July 2026 (RC4 deprecation, CVE‑2026‑20833) removed this safety net, and ten years of technical debt came to a head in a matter of hours: failed cross-domain authentication, AD replication returning “Access Denied,” and inaccessible shares.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
