{"id":192834,"date":"2017-08-07T00:46:44","date_gmt":"2017-08-06T22:46:44","guid":{"rendered":"http:\/\/www.borncity.com\/blog\/?p=192834"},"modified":"2017-08-07T00:47:22","modified_gmt":"2017-08-06T22:47:22","slug":"ubuntu-google-gpg-error-beheben","status":"publish","type":"post","link":"https:\/\/borncity.com\/blog\/2017\/08\/07\/ubuntu-google-gpg-error-beheben\/","title":{"rendered":"Ubuntu: Google GPG Error beheben"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" style=\"float: left; margin: 0px 10px 0px 0px; display: inline\" src=\"https:\/\/borncity.com\/blog\/wp-content\/uploads\/2015\/11\/Linux.jpg\" width=\"64\" height=\"76\"\/>Seit dem 4. August 2017 gibt es einen GPG-Fehler, sobald der Befehl <em>apt update<\/em> eingegeben wird. Hintergrund ist wohl, dass der \u00f6ffentliche GPG-Key, den Google zum Signieren eigenen Codes f\u00fcr die Linux-Repositories verwendet, ge\u00e4ndert wurde. <\/p>\n<p><!--more--><\/p>\n<p>Wer unter Ubuntu den Befehl <em>apt update<\/em> ausf\u00fchrt, erh\u00e4lt dann die in nachfolgendem Screenshot gezeigte Fehlermeldung. <\/p>\n<p><a href=\"http:\/\/www.omgubuntu.co.uk\/wp-content\/uploads\/2017\/08\/Screen-Shot-2017-08-06-at-21.55.13-750x192.png\" target=\"_blank\"><img loading=\"lazy\" decoding=\"async\" title=\"Google GPG Error \" alt=\"Google GPG Error \" src=\"http:\/\/www.omgubuntu.co.uk\/wp-content\/uploads\/2017\/08\/Screen-Shot-2017-08-06-at-21.55.13-750x192.png\" width=\"648\" height=\"166\"\/><\/a><\/p>\n<blockquote>\n<p>W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: dl.google.com\/linux\/chrome\/d\u2026 stable Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6494C6D6997C215E<\/p>\n<p>W: Failed to fetch dl.google.com\/linux\/chrome\/deb stable Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6494C6D6997C215E<\/p>\n<p>W: Some index files failed to download. They have been ignored, or old ones used instead.<br \/>Google signs its packages with GPG keys so that you (and your package manager) can \"verify product updates\". When a GPG expires, changes, or is otherwise missing from your system your package manager will display an error, which is precisely what the monospaced gunk above is.<\/p>\n<\/blockquote>\n<p>Der apt-Befehl findet keinen \u00f6ffentlichen GPG-Schl\u00fcssel und bricht das Update ab. Zum Fixen dieses Problems l\u00e4sst sich folgender Befehl in einem Terminalfenster verwenden:<\/p>\n<pre>wget -q -O - https:\/\/dl.google.com\/linux\/linux_signing_key.pub | sudo apt-key add -<\/pre>\n<p>Es sollte eine Passwortabfrage erscheinen und dann m\u00fcsste der <em>apt update<\/em>-Befehl wieder durchlaufen. Mehr Details finden sich in <a href=\"http:\/\/www.omgubuntu.co.uk\/2017\/08\/fix-google-gpg-key-linux-repository-error\" target=\"_blank\">diesem Beitrag<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Seit dem 4. August 2017 gibt es einen GPG-Fehler, sobald der Befehl apt update eingegeben wird. Hintergrund ist wohl, dass der \u00f6ffentliche GPG-Key, den Google zum Signieren eigenen Codes f\u00fcr die Linux-Repositories verwendet, ge\u00e4ndert wurde.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11],"tags":[636,3188,405,4347],"class_list":["post-192834","post","type-post","status-publish","format-standard","hentry","category-problemlosung","tag-error","tag-fix","tag-google","tag-ubuntu"],"_links":{"self":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/192834","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/comments?post=192834"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/192834\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/media?parent=192834"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/categories?post=192834"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/tags?post=192834"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}