<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Cryptography on blog katexochen</title>
    <link>https://katexochen.aro.bz/tags/cryptography/</link>
    <description>Recent content in Cryptography on blog katexochen</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>Paul Meyer</copyright>
    <lastBuildDate>Wed, 29 Apr 2026 09:00:00 +0200</lastBuildDate>
    <atom:link href="https://katexochen.aro.bz/tags/cryptography/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Secure signatures without a private key</title>
      <link>https://katexochen.aro.bz/posts/reproducible-secure-signatures/</link>
      <pubDate>Wed, 29 Apr 2026 09:00:00 +0200</pubDate>
      <guid>https://katexochen.aro.bz/posts/reproducible-secure-signatures/</guid>
      <description>&lt;p&gt;&lt;em&gt;Reproducible builds allow anyone to verify that a binary matches its source code.
But what if the build artifact must contain a cryptographic signature?
Reproducing the signature requires the private key, which defeats the purpose of reproducibility.
In this post, we present a technique based on ECDSA public key recovery that produces signatures which are both secure and fully reproducible, without anyone ever knowing a private key.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;build-artifacts-with-signatures---a-reproducibility-issue&#34;&gt;Build artifacts with signatures - a reproducibility issue&lt;/h2&gt;
&lt;p&gt;Remote attestation is a fundamental part of Confidential Computing.
It can be used to prove what software is running in a remote environment.
Users of such an attested environment do not need to trust the software vendor, excluding them from the trusted computing base&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
