<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Webpki on TurboLight Solutions</title><link>https://www.turbolightsolutions.com/tags/webpki/</link><description>Recent content in Webpki on TurboLight Solutions</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 23 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.turbolightsolutions.com/tags/webpki/index.xml" rel="self" type="application/rss+xml"/><item><title>Certificate Profiles Need a Single Source of Truth</title><link>https://www.turbolightsolutions.com/posts/certificate-profiles-need-a-single-source-of-truth/</link><pubDate>Thu, 23 Jul 2026 00:00:00 +0000</pubDate><guid>https://www.turbolightsolutions.com/posts/certificate-profiles-need-a-single-source-of-truth/</guid><description>&lt;p&gt;A CA&amp;rsquo;s certificate profile exists in at least three places: the policy documents (CP/CPS) that
describes it in prose, the CA software configuration that actually produces
certificates, and in user-facing product documentation. Those artifacts are
maintained separately, usually by different teams, and nothing forces them to agree.&lt;/p&gt;
&lt;p&gt;Software engineering named this problem decades ago. &lt;strong&gt;&amp;ldquo;Don&amp;rsquo;t Repeat Yourself&amp;rdquo;&lt;/strong&gt; is the rule that every piece of knowledge must
have a single, authoritative representation within a system. If information is duplicated, it will
eventually be changed in one place and not the others, and the copies will silently
disagree. But what happens when they &lt;strong&gt;do&lt;/strong&gt; disagree?&lt;/p&gt;</description></item></channel></rss>