<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Certificate-Management on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/certificate-management/</link>
    <description>Recent content in Certificate-Management on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 09 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/certificate-management/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted SSH Certificate Management: step-ca vs Vault vs Teleport (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-05-09-self-hosted-ssh-certificate-management-step-ca-vault-teleport/</link>
      <pubDate>Sat, 09 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-09-self-hosted-ssh-certificate-management-step-ca-vault-teleport/</guid>
      <description>&lt;p&gt;Managing SSH access at scale is one of the most common infrastructure challenges. Traditional SSH key management relies on distributing public keys via &lt;code&gt;authorized_keys&lt;/code&gt; files, which becomes unwieldy as teams grow: keys are rarely rotated, departed employees retain access, and auditing who accessed what server is nearly impossible.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
