<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Verification on sec.schmolka.org</title><link>https://sec.schmolka.org/tags/verification/</link><description>Recent content in Verification on sec.schmolka.org</description><generator>Hugo</generator><language>en-GB</language><lastBuildDate>Thu, 15 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://sec.schmolka.org/tags/verification/index.xml" rel="self" type="application/rss+xml"/><item><title>Assumptions on the Chain of Trust</title><link>https://sec.schmolka.org/posts/2026-10-15-assumptions-on-the-chain-of-trust/</link><pubDate>Thu, 15 Oct 2026 00:00:00 +0000</pubDate><guid>https://sec.schmolka.org/posts/2026-10-15-assumptions-on-the-chain-of-trust/</guid><description>&lt;p&gt;For a security architecture to verify anything, it needs to parse data. After parsing, the (hopefully) cryptographically sound algorithms can do their job and prove that e.g. the kernel&amp;rsquo;s signature is valid and that it can be loaded. But who verifies the parsing?&lt;/p&gt;&#10;&lt;h2 id="what-is-the-chain-of-trust-and-why-does-it-work"&gt;What is the Chain of Trust and why does it work?&lt;/h2&gt;&#10;&lt;p&gt;The Chain of Trust is a concept in which each part of a system verifies the authenticity of another element, with trust flowing from a root node.&#10;In embedded systems, this is usually something you can physically control, but can also be something you simply choose to trust (such as a root CA for certificates).&lt;/p&gt;</description></item></channel></rss>