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

Ubuntu Xenial: apt.key uses weak digist algorithm. #1414

Closed
torkelsson opened this issue Jun 28, 2016 · 3 comments
Closed

Ubuntu Xenial: apt.key uses weak digist algorithm. #1414

torkelsson opened this issue Jun 28, 2016 · 3 comments

Comments

@torkelsson
Copy link

I'm trying to install xcat on a Ubuntu Xenial system. After adding the apt-key (wget -O - "http://xcat.org/files/xcat/repos/apt/apt.key" | apt-key add -) to the keyring and running apt-get update I get:

W: https://xcat.org/files/xcat/repos/apt/2.12/core-snap/dists/xenial/InRelease: Signature by key F75B1BF678B644FDF3AACFC860A3E9ACC6565BC9 uses weak digest algorithm (SHA1)
W: https://xcat.org/files/xcat/repos/apt/xcat-dep/dists/xenial/InRelease: Signature by key F75B1BF678B644FDF3AACFC860A3E9ACC6565BC9 uses weak digest algorithm (SHA1)

Can you please update the apt-key to a more modern?

@daniceexi daniceexi self-assigned this Jun 29, 2016
@daniceexi daniceexi added this to the 2.12.2 milestone Jun 29, 2016
@daniceexi
Copy link
Contributor

Thanks for the information, it will be fixed in next release.

@zet809 zet809 modified the milestones: 2.12.3, 2.12.2 Aug 12, 2016
@immarvin immarvin modified the milestones: 2.12.4, 2.12.3 Sep 26, 2016
@immarvin immarvin modified the milestones: 2.13, 2.12.4 Nov 7, 2016
@immarvin immarvin modified the milestones: 2.14, 2.13 Nov 25, 2016
@immarvin immarvin assigned immarvin and unassigned daniceexi Mar 6, 2017
@zet809 zet809 removed this from the 2.14 milestone Mar 26, 2018
@immarvin
Copy link
Contributor

will take a look when supporting ubuntu 18.04

@neo954
Copy link
Contributor

neo954 commented Jun 21, 2018

I will close this issue right here. The problem will be tracked though issue #5306.

@neo954 neo954 closed this as completed Jun 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants