Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Warning message about key 97D2B6FC0D3BCB4ABC56679C11B01C94D1BE1726 #1

Open
ralphlange opened this issue Apr 3, 2016 · 2 comments
Open
Assignees

Comments

@ralphlange
Copy link

Updating my Debian testing system, I start seeing messages like:

W: http://epics.nsls2.bnl.gov/debian/dists/wheezy/InRelease: Signature by key 97D2B6FC0D3BCB4ABC56679C11B01C94D1BE1726 uses weak digest algorithm (SHA1)
W: http://epics.nsls2.bnl.gov/debian/dists/wheezy/staging/InRelease: Signature by key 97D2B6FC0D3BCB4ABC56679C11B01C94D1BE1726 uses weak digest algorithm (SHA1)
@jrcoding
Copy link

jrcoding commented Apr 4, 2016

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.

@mdavidsaver
Copy link

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.

To verify

$ echo test > test
$ gpg -o test.sig --sign test
$ gpg -v --verify test.sib
...
gpg: binary signature, digest algorithm SHA256

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants