Bug#818405: apt: Google Chrome repository unusable because of weak digest
On 28/03/16 11:14, Julian Andres Klode wrote:
Don't be rude: Don't play hidden bts control message games.
Julian, I apologise for inadvertently reopening this bug. That was not
my intent (and I have now re-read the bts docs).
I am quite happy with this bug being closed as a won't-fix and was
simply trying to provide updated information for the benefit of other
affected users and as feedback to you (as the reporter-to-Google).
Just remove the freaking talkplugin thing. It
(a) makes no sense at all to have that if you use Chrome
(b) it's dead, aka not maintained anymore
Thanks very much. I had no idea that Hangouts under Chrome no longer
required talkplugin. Purged!
The other thing is a *warning* and does not cause any trouble at all. Heck,
most frontends even ignore it. Please read
https://wiki.debian.org/Teams/Apt/Sha1Removal
I have been following updates to this page and my only concern was for
talkplugin (now fixed by following your advice).
I am aware that the chome repo error is only a warning and can confirm a
successful upgrade last week to google-chrome-stable 49.0.2623.108-1
amd64, after SHA1 support was removed in apt.
Kind regards,
--
Ben Caradoc-Davies <ben@transient.nz>
Director
Transient Software Limited <http://transient.nz/>
New Zealand
Reply to: