<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Certificate-Authority on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/certificate-authority/</link>
    <description>Recent content in Certificate-Authority on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 26 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/certificate-authority/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>EJBCA vs Dogtag PKI vs OpenXPKI: Self-Hosted Enterprise CA Guide 2026</title>
      <link>https://www.pistack.xyz/posts/2026-04-26-ejbca-vs-dogtag-pki-vs-openxpki-self-hosted-enterprise-ca-guide/</link>
      <pubDate>Sun, 26 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-04-26-ejbca-vs-dogtag-pki-vs-openxpki-self-hosted-enterprise-ca-guide/</guid>
      <description>&lt;p&gt;Running your own certificate authority (CA) is essential for organizations that need full control over certificate issuance, lifecycle management, and cryptographic policy enforcement. While lightweight tools like &lt;a href=&#34;https://smallstep.com/&#34;&gt;smallstep CA&lt;/a&gt; work well for SSH certificates and web-scale TLS automation, enterprise environments demand more: certificate enrollment workflows, hardware security module (HSM) integration, compliance reporting, and granular policy control.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
