<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Code-Signing on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/code-signing/</link>
    <description>Recent content in Code-Signing on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 12 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/code-signing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Git Commit Signing: GPG vs SSH vs Sigstore Cosign Guide 2026</title>
      <link>https://www.pistack.xyz/posts/2026-05-12-self-hosted-git-commit-signing-gpg-ssh-sigstore-cosign-guide/</link>
      <pubDate>Tue, 12 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-12-self-hosted-git-commit-signing-gpg-ssh-sigstore-cosign-guide/</guid>
      <description>&lt;p&gt;Every commit pushed to a shared repository carries an implicit claim about authorship, but without cryptographic verification, anyone can forge another developer&amp;rsquo;s identity in the commit log. Git commit signing solves this by attaching a cryptographic signature to each commit, proving that the code originated from a trusted key holder.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
