bps
(Pascal Bertrand)
October 1, 2026, 4:22am
1
Hello,
Just ran apt update on an ubuntu 24.04 server and got:
Err:6 ``https://dl.cloudsmith.io/public/caddy/stable/deb/debian`` any-version InRelease
The following signatures were invalid: EXPKEYSIG 531A6B20FA058A70 Caddy Web Server <contact@caddyserver.com>
After inspecting the key, I deleted it before downloading as per Install — Caddy Documentation . Cleared apt’s cache for dl.cloudsmith.io before trying apt update again. No luck.
$ gpg --show-keys /usr/share/keyrings/caddy-stable-archive-keyring.gpg
pub rsa4096 2016-04-01 [SC]
65760C51EDEA2017CEA2CA15155B6D79CA56EA34
uid Caddy Web Server contact@caddyserver.com
sub rsa2048 2016-04-01 [E] [expired: 2024-03-30]
sub rsa2048 2016-04-01 [SA] [expired: 2024-03-30]
sub rsa4096 2020-12-29 [S]
gpg: WARNING: No valid encryption subkey left over.
Can someone handling the debian repository take a look at this?
I can confirm the same issue on Debian 13 (Trixie).
APT/sqv rejects the same signing subkey :
531A6B20FA058A70
I also inspected the current InRelease directly :
https://dl.cloudsmith.io/public/caddy/stable/deb/debian/dists/any-version/InRelease
It reports :
Date : Thu, 01 Oct 2026 04:17:47 UTC
The OpenPGP signature identifies:
keyid 531A6B20FA058A70
issuer fingerprint :
D59FC5219C50B989D95FCE4E531A6B20FA058A70
signature created :
2026-10-01
That signing subkey expired on 2024-03-30.
So the current InRelease appears to have been freshly generated today
while still being signed with the expired subkey.
I have also opened a ticket with Cloudsmith support and provided them
with the diagnostic information.
bps
(Pascal Bertrand)
October 1, 2026, 10:14pm
3
Can confirm it is fixed today. 2.11.6 installed correctly. I guess it was signed with one of the expired keys yesterday.
Thank you to whoever go it fixed.
See Github issue for the discussion
opened 10:52PM - 30 Sep 26 UTC
closed 03:13PM - 01 Oct 26 UTC
CI/CD
### Issue Details
The Cloudsmith repo `caddy/stable` is still signing `InReleas… e` with subkey `D59FC5219C50B989D95FCE4E531A6B20FA058A70`, which expired on 2024-03-30. The published `gpg.key` contains a valid rsa4096 signing subkey (created 2020-12-29), but it is not being used.
On Debian 13 (trixie, arm64), apt verifies signatures with `sqv`, which rejects this:
```
Signing key on 65760C51EDEA2017CEA2CA15155B6D79CA56EA34 is bad: The subkey is not live because: Expired on 2024-03-30T17:07:45Z
```
`gpg --verify` on the current InRelease confirms it uses the expired subkey:
```
gpg: Signature made Thu 01 Oct 2026 12:42:06 AM CEST
gpg: using RSA key D59FC5219C50B989D95FCE4E531A6B20FA058A70
gpg: Good signature from "Caddy Web Server <contact@caddyserver.com>" [unknown]
gpg: Note: This key has expired!
```
Expected: sign with the valid 2020 subkey, or extend the expiry of the old one.
### Assistance Disclosure
AI used
### If AI was used, describe the extent to which it was used.
I used Claude (Anthropic) to help interpret the apt/sqv error and draft this issue text. All commands were run and all output was verified by me on my own system.