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
The repository owner needs to pass --digest-algo SHA512 or --digest-algo SHA256 (or another SHA2 algorithm) to gpg when signing the file. Repositories with DSA keys need to be migrated to RSA first.
I would attempt a PR, but I'm not familiar with Go's package builder, and from e3bb01a it's not entirely clear where the build scripts / dependencies are coming from - possibly dh or possibly outside the repo entirely?
The text was updated successfully, but these errors were encountered:
I'm getting the following when running apt update on Ubuntu 17.04:
W: GPG error: https://apt.gemnasium.com stable Release: The following signatures were invalid: 0D6C9B7583A02B8642898D3AE5CEAB0AC5F1CA2A
E: The repository 'https://apt.gemnasium.com stable Release' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
If I download Release and Release.gpg and validate it manually, it's fine.
I think this may be caused by the old digest algorithm.
When running
apt update
on Ubuntu 16.04 a warning message is displayed:W: http://apt.gemnasium.com/dists/stable/Release.gpg: Signature by key 0D6C9B7583A02B8642898D3AE5CEAB0AC5F1CA2A uses weak digest algorithm (SHA1)
http://askubuntu.com/a/764981 has more details, with a link to the Debian wiki on the subject noting that they will be changing that to an error starting in January 2017.
To fix the problem, from the wiki:
I would attempt a PR, but I'm not familiar with Go's package builder, and from e3bb01a it's not entirely clear where the build scripts / dependencies are coming from - possibly
dh
or possibly outside the repo entirely?The text was updated successfully, but these errors were encountered: