<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pki on Lead DevOps</title><link>https://lead-devops.blackdevhub.online/en/tags/pki/</link><description>Recent content in Pki on Lead DevOps</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 31 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://lead-devops.blackdevhub.online/en/tags/pki/index.xml" rel="self" type="application/rss+xml"/><item><title>Trusting a custom CA: system store, browsers, and CLI</title><link>https://lead-devops.blackdevhub.online/en/posts/trust-custom-ca/</link><pubDate>Mon, 31 Aug 2026 00:00:00 +0000</pubDate><guid>https://lead-devops.blackdevhub.online/en/posts/trust-custom-ca/</guid><description>&lt;p&gt;A TLS error that says the certificate is untrusted almost never means the certificate is “broken”. The &lt;strong&gt;trust anchor&lt;/strong&gt; is in the wrong store.&lt;/p&gt;
&lt;p&gt;&lt;code&gt;curl&lt;/code&gt;, &lt;code&gt;openssl&lt;/code&gt;, Git, Python, and the browser are different clients. Some keep their own root lists. Updating the OS bundle on Linux will not fix Chrome or Firefox by itself.&lt;/p&gt;
&lt;h2 id="what-to-import"&gt;What to import&lt;/h2&gt;
&lt;p&gt;You trust the &lt;strong&gt;CA root&lt;/strong&gt; that signed the server certificate, not &lt;code&gt;localhost.crt&lt;/code&gt; / &lt;code&gt;app.example.internal&lt;/code&gt; itself.&lt;/p&gt;</description></item></channel></rss>