<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>key-transparency on Late Night Thinking</title>
    <link>https://kula.tproa.net/tags/key-transparency/</link>
    <description>Recent content in key-transparency on Late Night Thinking</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>&amp;copy; 2020-2025. All rights reserved.</copyright>
    <lastBuildDate>Thu, 22 Oct 2026 00:30:36 +0000</lastBuildDate><atom:link href="https://kula.tproa.net/tags/key-transparency/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Figuring out how Sigsum works, Part 1</title>
      <link>https://kula.tproa.net/lnt/2026/10/figuring-out-how-sigsum-works-part-1/</link>
      <pubDate>Thu, 22 Oct 2026 00:30:36 +0000</pubDate>
      
      <guid>https://kula.tproa.net/lnt/2026/10/figuring-out-how-sigsum-works-part-1/</guid>
      <description>After I finished the primary work on my Internal Certificate Authority I started down another rabbit hole which has led me even further from the original reason I created the internal CA to begin with. My tooling takes a snapshot of the Vault data, and I wanted to keep some sort of audit log. I have a normal backup process for the data, but I want to make checksums of the data and configuration, and then publish that to some sort of public record so the next time I need to use the CA, I can verify the state.</description>
    </item>
    
  </channel>
</rss>
