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

RFE: always use SHA256 digests in Release file signatures #73

Open
ktdreyer opened this issue Jan 23, 2019 · 1 comment
Open

RFE: always use SHA256 digests in Release file signatures #73

ktdreyer opened this issue Jan 23, 2019 · 1 comment

Comments

@ktdreyer
Copy link
Member

Apt on Ubuntu Xenial (and newer) will warn if the Apt repo GPG signatures are SHA1 instead of SHA256.

Background links:

By default, gnupg2 has a sha1 digest algorithm.

As a workaround, a long time ago I added "digest-algo sha256" to the gpg.conf file on the local signer system, like so:

# See http://askubuntu.com/questions/819641/reprepro-signature-by-key-uses-weak-digest-algorithm-sha1
# and https://juliank.wordpress.com/2016/03/14/dropping-sha-1-support-in-apt/
digest-algo sha256

It would be more robust if merfi ran gpg2 with the --digest-algo SHA256 argument every time, so we did not depend on the state of the local .gpg.conf file.

@ktdreyer
Copy link
Member Author

This might be resolved in the very latest GnuPG 2. It seems like Fedora 29 signs with SHA256 by default.

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

1 participant