mirror of
https://github.com/binwiederhier/ntfy.git
synced 2026-05-09 16:35:53 +02:00
[GH-ISSUE #1586] APT repository key still using SHA1 - now causing "Missing key" errors #1115
Labels
No labels
ai-generated
android-app
android-app
android-app
🪲 bug
build
build
dependencies
docs
enhancement
enhancement
🔥 HOT
in-progress 🏃
ios
prio:low
prio:low
pull-request
question
🔒 security
server
server
unified-push
web-app
website
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ntfy#1115
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Tealk on GitHub (Feb 1, 2026).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1586
Description:
The ntfy Debian repository at
https://archive.heckel.io/apt/is failing to update due to SHA1 signature deprecation (deadline: 2026-02-01).Error Messages:
System Information:
Root Cause:
The signing key
CF871F1E8399DAEF470832661D5B8EDFB2476E53carries only SHA1 self-signatures. As of February 1, 2026, Debian's apt policy rejects SHA1-based signatures .Solution:
Update the repository signing key to use SHA256 or SHA512 for all signatures and re-sign the repository metadata accordingly .
Related Issues:
@binwiederhier commented on GitHub (Feb 1, 2026):
As per the two linked issues and the docs, this is not the official repo anymore. See https://docs.ntfy.sh/install/#debianubuntu-repository
@Tealk commented on GitHub (Feb 1, 2026):
Oh sorry, I somehow missed that thing with the repo; I was probably too focused on the key.