<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>GPG on Cloudkaramchari</title><link>https://www.cloudkaramchari.com/tags/gpg/</link><description>Recent content in GPG on Cloudkaramchari</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>cloudkaramchari</copyright><lastBuildDate>Fri, 11 Sep 2026 19:39:32 +0530</lastBuildDate><atom:link href="https://www.cloudkaramchari.com/tags/gpg/index.xml" rel="self" type="application/rss+xml"/><item><title>Fix GitHub CLI NO_PUBKEY / EXPKEYSIG Errors After the September 2026 Key Rotation</title><link>https://www.cloudkaramchari.com/blog/fix-github-cli-gpg-no-pubkey-signing-key-expired-error-linux/</link><pubDate>Fri, 11 Sep 2026 19:39:32 +0530</pubDate><guid>https://www.cloudkaramchari.com/blog/fix-github-cli-gpg-no-pubkey-signing-key-expired-error-linux/</guid><description>
&lt;h1 id="fix-github-cli-no_pubkey--expkeysig-errors-after-the-september-2026-key-rotation">Fix GitHub CLI NO_PUBKEY / EXPKEYSIG Errors After the September 2026 Key Rotation&lt;/h1>
&lt;p>If &lt;code>apt update&lt;/code>, &lt;code>dnf update gh&lt;/code>, or &lt;code>yum update gh&lt;/code> suddenly started failing on a Linux box that has the GitHub CLI installed from GitHub's own package repository, you're not imagining it. The PGP key GitHub CLI used to sign its Linux packages and repository metadata expired on &lt;strong>September 5, 2026&lt;/strong>, and any system that hadn't picked up the replacement key by then starts throwing signature verification failures on every package operation — not just &lt;code>gh&lt;/code> upgrades.&lt;/p></description></item></channel></rss>