Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #165551
| From | Sven Hartge <sven@svenhartge.de> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: weak repository key |
| Date | 2016-03-17 18:20 +0100 |
| Message-ID | <rdJKy-1PB-17@gated-at.bofh.it> (permalink) |
| References | <rdIv8-Qo-19@gated-at.bofh.it> <rdIv8-Qo-29@gated-at.bofh.it> |
| Organization | Newsfeed am Wurmloch |
Jochen Spieker <ml@well-adjusted.de> wrote: > Floris: >> After updating to apt version 1.2.7 I get a warning on apt-get update: >> W: gpgv:/var/lib/apt/lists/partial/dl.google.com_linux_chrome_deb_dists_stable_Release.gpg: >> The repository is insufficiently signed by key >> 4CCA1EAF950CEE4AB83976DCA040830F7FAC5991 (weak digest) >> >> and the repository is ignored >> >> Is there a way that apt re-trust the old SHA1 key, or do we have to report >> this to Google and all other repos? > Report it: > https://lists.debian.org/debian-devel-announce/2016/03/msg00006.html According to https://bugs.chromium.org/p/chromium/issues/detail?id=594414 this should be fixed with the next repository update. Grüße, Sven. -- Sigmentation fault. Core dumped.
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
weak repository key Floris <jkfloris@dds.nl> - 2016-03-17 17:00 +0100
Re: weak repository key Jochen Spieker <ml@well-adjusted.de> - 2016-03-17 17:00 +0100
Re: weak repository key Sven Hartge <sven@svenhartge.de> - 2016-03-17 18:20 +0100
Re: Re: weak repository key Daniel Schröter <d.schroeter@gmx.de> - 2016-03-28 21:20 +0200
Re: weak repository key Sven Hartge <sven@svenhartge.de> - 2016-03-28 21:50 +0200
Re: weak repository key The Wanderer <wanderer@fastmail.fm> - 2016-03-29 16:00 +0200
csiph-web