You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Correct, seems the key has been generated with gpg option 'cert-digest-algo SHA1'.
Because in near future apt will deny using keys which are generated with SHA1 newer apt versions now complain.
We had the same problem with our local debian repo. The cure is to install a new key generated with the gpg option 'cert-digest-algo SHA512'.
Of course a job for the repo maintainer.
No need to replace the key to fix this. Use gpg --edit-key D1BE1726 and update the algorithm preferences. Simplest way to do this is simply to use a more recent version of gpg, run setpref with no arguments and accept the defaults.
It might also be necessary set cert-digest-algo or personal-digest-preferences in gpg.conf.
Updating my Debian testing system, I start seeing messages like:
The text was updated successfully, but these errors were encountered: