<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Public Key Infrastructure on Nalar</title>
    <link>https://nalar.dev/tags/public-key-infrastructure/</link>
    <description>Recent content in Public Key Infrastructure on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 21 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/public-key-infrastructure/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>SSH Certificates Shift Access Trust to a Signing Authority</title>
      <link>https://nalar.dev/ssh-certificates-shift-access-trust-to-a-signing-authority/</link>
      <pubDate>Mon, 21 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/ssh-certificates-shift-access-trust-to-a-signing-authority/</guid>
      <description>&lt;h1 id=&#34;ssh-certificates-shift-access-trust-to-a-signing-authority&#34;&gt;SSH Certificates Shift Access Trust to a Signing Authority&lt;/h1&gt;&#xA;&lt;p&gt;Public-key SSH access often starts with a simple mapping: place a user&amp;rsquo;s public key in &lt;code&gt;authorized_keys&lt;/code&gt;, keep the private key with the user, and let the server accept possession of the matching private key. The model is direct and effective, but its administrative cost rises as people and hosts multiply. Every host can become another place where access state must be added, audited, and removed.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
