![]() ![]() This of course is NOT a fix for anything at the moment, but will configure everything properly again. The file should look like this: repo_add_once="true" deb again, just make sure you set the repo_add_once variable to "true" in /etc/defaults/google-chrome. Software-properties-gtk will allow you to remove any of Google's existing signatures in the authentication tab, before adding the new ones.Īnd if you've deleted the repo files (like I did several times today) you can setup the repos properly by installing the. If you're frustrated with the messages, you can disable them by commenting out the sources in /etc/apt//google-chrome.list. It should be easy to add the latest ones with: wget -q -O - | sudo apt-key add -Īssuming of course that the link to the new keys doesn't change I'm going to be keeping an eye out for changes there. I suspect this is just a matter of time, and we should see a fix soon(ish),in the form of new GPG pubkey signatures we should be using. If this turns out to be true, besides being incredibly annoying, there's not much we can do until Google gets their act together. This might mean they've created hashes for new keys, but have yet to publish new GPG pubkey sigs to go with them for the repo, hence the hash mismatch. Google may have rolled out new hashes that no longer match the GPG pub key signatures that everyone is using, presumably these are no longer sha1sums. The following is speculative, but seems to fit the symptoms we're seeing: Google was going to provide a fix for the "weak digest algorithm".apt deprecated sha1 recently, which explains the warnings we have been getting from the google repo since the latest LTS was released.The source of this problem seems to be twofold: I'm getting this same exact error "hash sum mismatch" on both Ubuntu 14.04 as well as Ubuntu 16.04, and only 16.04 complains about the encryption algorithm. This isn't a deal breaker for me since now apt-get returns 0 and I can run sudo apt-get update
0 Comments
Leave a Reply. |