Eddie Desktop - APT Repository Signing Key Update

[Staff 10438]

Starting from February 1st, 2026, Debian (e.g. Trixie) enforces stricter OpenPGP policies and no longer accepts repository signatures involving SHA1-based certifications.

As a result, users may see errors such as:
 

Get:4 http://eddie.website/repository/apt stable InRelease [3,954 B]         
Err:4 http://eddie.website/repository/apt stable InRelease
  Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on C181AC89FA667E317F423998513EFC94400D7698 is not bound:            No binding signature at time 2025-01-14T13:07:46Z   because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance   because: SHA1 is not considered secure since 2026-02-01T00:00:00Z
Warning: OpenPGP signature verification failed: http://eddie.website/repository/apt stable InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on C181AC89FA667E317F423998513EFC94400D7698 is not bound:            No binding signature at time 2025-01-14T13:07:46Z   because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance   because: SHA1 is not considered secure since 2026-02-01T00:00:00Z
Error: The repository 'http://eddie.website/repository/apt stable InRelease' is not signed.
Notice: Updating from such a repository can't be done securely, and is therefore disabled by default.
Notice: See apt-secure(8) manpage for repository creation and user configuration details.

This was caused by an outdated signing key certification used by the repository.
 

Solution

The repository signing key has been regenerated and the repository is now correctly signed again.
To restore updates, please re-import the updated maintainer key:
 

curl -fsSL https://eddie.website/repository/keys/eddie_maintainer_gpg.key | sudo tee /usr/share/keyrings/eddie.website-keyring.asc > /dev/null

Then run:
 

sudo apt update

Sorry for the inconvenience, and thanks for your patience.

Kind regards
 

[airxirtir 3]

Thanks a lot for the quick fix and the clear instructions!

I removed my temporary Sequoia policy workaround, re-imported the updated maintainer key as posted, and apt update is working again on Debian Trixie.

Much appreciated.