<?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>Adcs on Aperture Zone</title>
    <link>https://aperturezone.com/tags/adcs/</link>
    <description>Recent content in Adcs 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>Wed, 14 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aperturezone.com/tags/adcs/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>PKI: One Infrastructure, Two Authorities</title>
      <link>https://aperturezone.com/pki/</link>
      <pubDate>Wed, 14 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/pki/</guid>
      <description>&lt;p&gt;A PKI migration story told from start to finish, in three parts. On the Linux and appliance side: a manual OpenSSL CA replaced by step-ca, with short-lived certificates that renew automatically. On the Microsoft side: AD CS kept separate for RDP and autoenrollment. Finally, signing .rdp files following the April 2026 security hardening.&lt;/p&gt;
&lt;!--TUILES--&gt;</description>
    </item>
    
  </channel>
</rss>
