“在签名验证期间发生错误”。在添加密钥3A79BD29和sudo apt-key del< old-key> gt; gt;之后,在适当的情况下在Debian上
我使用的服务器是Debian 9.13 OS和“ MySQL Ver 14.14 Distrib 5.7.34”。 我尝试通过以下命令从所有配置的源下载软件包信息:
sudo apt update
然后我面对以下错误:
Hit:1 http://security.debian.org stretch/updates InRelease
Hit:2 http://packages.cloud.google.com/apt google-cloud-monitoring-stretch-all InRelease
Hit:3 http://packages.cloud.google.com/apt cloud-sdk-stretch InRelease
Hit:4 http://packages.cloud.google.com/apt google-compute-engine-stretch-stable InRelease
Ign:5 http://deb.debian.org/debian stretch InRelease
Hit:6 http://repo.mysql.com/apt/debian stretch InRelease
Hit:7 http://packages.cloud.google.com/apt google-cloud-packages-archive-keyring-stretch InRelease
Hit:8 http://deb.debian.org/debian stretch-updates InRelease
Hit:9 https://packages.cloud.google.com/apt google-cloud-logging-stretch-all InRelease
Hit:10 http://deb.debian.org/debian stretch-backports InRelease
Hit:11 http://deb.debian.org/debian stretch Release
Get:12 https://packages.sury.org/php stretch InRelease [6,839 B]
Err:6 http://repo.mysql.com/apt/debian stretch InRelease
The following signatures were invalid: EXPKEYSIG 8C718D3B5072E1F5 MySQL Release Engineering <[email protected]>
Err:12 https://packages.sury.org/php stretch InRelease
The following signatures were invalid: EXPKEYSIG B188E2B695BD4743 DEB.SURY.ORG Automatic Signing Key <[email protected]>
Fetched 6,839 B in 1s (5,504 B/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
10 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://repo.mysql.com/apt/debian stretch InRelease: The following signatures were invalid: EXPKEYSIG 8C718D3B5072E1F5 MySQL Release Engineering <[email protected]>
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://packages.sury.org/php stretch InRelease: The following signatures were invalid: EXPKEYSIG B188E2B695BD4743 DEB.SURY.ORG Automatic Signing Key <[email protected]>
W: Failed to fetch http://repo.mysql.com/apt/debian/dists/stretch/InRelease The following signatures were invalid: EXPKEYSIG 8C718D3B5072E1F5 MySQL Release Engineering <[email protected]>
W: Failed to fetch https://packages.sury.org/php/dists/stretch/InRelease The following signatures were invalid: EXPKEYSIG B188E2B695BD4743 DEB.SURY.ORG Automatic Signing Key <[email protected]>
W: Some index files failed to download. They have been ignored, or old ones used instead.
然后,我要解决漫长的旅程并遇到一些问题的过期签名问题,所以我以为我以为也许我做了一些错误,所以我在详细说明了我遵循的集合。 重新恢复后,我结识更新过期的键如下:
sudo apt-key list
然后我看到了:
/etc/apt/trusted.gpg
--------------------
pub dsa1024 2003-02-03 [SCA] [expired: 2022-02-16]
A4A9 4068 76FC BD3C 4567 70C8 8C71 8D3B 5072 E1F5
uid [ expired] MySQL Release Engineering <[email protected]>
pub rsa3072 2019-03-18 [SC] [expired: 2021-03-17]
1505 8500 A023 5D97 F5D1 0063 B188 E2B6 95BD 4743
uid [ expired] DEB.SURY.ORG Automatic Signing Key <[email protected]>
/etc/apt/trusted.gpg.d/debian-archive-bullseye-automatic.gpg
------------------------------------------------------------
pub rsa4096 2021-01-17 [SC] [expires: 2029-01-15]
1F89 983E 0081 FDE0 18F3 CC96 73A4 F27B 8DD4 7936
uid [ unknown] Debian Archive Automatic Signing Key (11/bullseye) <[email protected]>
sub rsa4096 2021-01-17 [S] [expires: 2029-01-15]
/etc/apt/trusted.gpg.d/debian-archive-bullseye-security-automatic.gpg
---------------------------------------------------------------------
pub rsa4096 2021-01-17 [SC] [expires: 2029-01-15]
AC53 0D52 0F2F 3269 F5E9 8313 A484 4904 4AAD 5C5D
uid [ unknown] Debian Security Archive Automatic Signing Key (11/bullseye) <[email protected]>
sub rsa4096 2021-01-17 [S] [expires: 2029-01-15]
/etc/apt/trusted.gpg.d/debian-archive-bullseye-stable.gpg
---------------------------------------------------------
pub rsa4096 2021-02-13 [SC] [expires: 2029-02-11]
A428 5295 FC7B 1A81 6000 62A9 605C 66F0 0D6C 9793
uid [ unknown] Debian Stable Release Key (11/bullseye) <[email protected]>
/etc/apt/trusted.gpg.d/debian-archive-buster-automatic.gpg
----------------------------------------------------------
pub rsa4096 2019-04-14 [SC] [expires: 2027-04-12]
80D1 5823 B7FD 1561 F9F7 BCDD DC30 D7C2 3CBB ABEE
uid [ unknown] Debian Archive Automatic Signing Key (10/buster) <[email protected]>
sub rsa4096 2019-04-14 [S] [expires: 2027-04-12]
/etc/apt/trusted.gpg.d/debian-archive-buster-security-automatic.gpg
-------------------------------------------------------------------
pub rsa4096 2019-04-14 [SC] [expires: 2027-04-12]
5E61 B217 265D A980 7A23 C5FF 4DFA B270 CAA9 6DFA
uid [ unknown] Debian Security Archive Automatic Signing Key (10/buster) <[email protected]>
sub rsa4096 2019-04-14 [S] [expires: 2027-04-12]
/etc/apt/trusted.gpg.d/debian-archive-buster-stable.gpg
-------------------------------------------------------
pub rsa4096 2019-02-05 [SC] [expires: 2027-02-03]
6D33 866E DD8F FA41 C014 3AED DCC9 EFBF 77E1 1517
uid [ unknown] Debian Stable Release Key (10/buster) <[email protected]>
/etc/apt/trusted.gpg.d/debian-archive-jessie-automatic.gpg
----------------------------------------------------------
pub rsa4096 2014-11-21 [SC] [expires: 2022-11-19]
126C 0D24 BD8A 2942 CC7D F8AC 7638 D044 2B90 D010
uid [ unknown] Debian Archive Automatic Signing Key (8/jessie) <[email protected]>
/etc/apt/trusted.gpg.d/debian-archive-jessie-security-automatic.gpg
-------------------------------------------------------------------
pub rsa4096 2014-11-21 [SC] [expires: 2022-11-19]
D211 6914 1CEC D440 F2EB 8DDA 9D6D 8F6B C857 C906
uid [ unknown] Debian Security Archive Automatic Signing Key (8/jessie) <[email protected]>
/etc/apt/trusted.gpg.d/debian-archive-jessie-stable.gpg
-------------------------------------------------------
pub rsa4096 2013-08-17 [SC] [expired: 2021-08-15]
75DD C3C4 A499 F1A1 8CB5 F3C8 CBF8 D6FD 518E 17E1
uid [ expired] Jessie Stable Release Key <[email protected]>
/etc/apt/trusted.gpg.d/debian-archive-stretch-automatic.gpg
-----------------------------------------------------------
pub rsa4096 2017-05-22 [SC] [expires: 2025-05-20]
E1CF 20DD FFE4 B89E 8026 58F1 E0B1 1894 F66A EC98
uid [ unknown] Debian Archive Automatic Signing Key (9/stretch) <[email protected]>
sub rsa4096 2017-05-22 [S] [expires: 2025-05-20]
/etc/apt/trusted.gpg.d/debian-archive-stretch-security-automatic.gpg
--------------------------------------------------------------------
pub rsa4096 2017-05-22 [SC] [expires: 2025-05-20]
6ED6 F5CB 5FA6 FB2F 460A E88E EDA0 D238 8AE2 2BA9
uid [ unknown] Debian Security Archive Automatic Signing Key (9/stretch) <[email protected]>
sub rsa4096 2017-05-22 [S] [expires: 2025-05-20]
/etc/apt/trusted.gpg.d/debian-archive-stretch-stable.gpg
--------------------------------------------------------
pub rsa4096 2017-05-20 [SC] [expires: 2025-05-18]
067E 3C45 6BAE 240A CEE8 8F6F EF0F 382A 1A7B 6500
uid [ unknown] Debian Stable Release Key (9/stretch) <[email protected]>
/etc/apt/trusted.gpg.d/google-cloud-packages-archive-keyring.gpg
----------------------------------------------------------------
pub rsa2048 2021-03-01 [SC] [expires: 2023-03-02]
7F92 E05B 3109 3BEF 5A3C 2D38 FEEA 9169 307E A071
uid [ unknown] Rapture Automatic Signing Key (cloud-rapture-signing-key-2021-03-01-08_01_09.pub)
sub rsa2048 2021-03-01 [E]
pub rsa2048 2020-12-04 [SC] [expires: 2022-12-04]
59FE 0256 8272 69DC 8157 8F92 8B57 C5C2 836F 4BEB
uid [ unknown] gLinux Rapture Automatic Signing Key (//depot/google3/production/borg/cloud-rapture/keys/cloud-rapture-pubkeys/cloud-rapture-signing-key-2020-12-03-16_08_05.pub) <[email protected]>
sub rsa2048 2020-12-04 [E]
因此,在此处显示的三个键已过期:
pub dsa1024 2003-02-03 [SCA] [expired: 2022-02-16]
A4A9 4068 76FC BD3C 4567 70C8 8C71 8D3B 5072 E1F5
uid [ expired] MySQL Release Engineering <[email protected]>
pub rsa3072 2019-03-18 [SC] [expired: 2021-03-17]
1505 8500 A023 5D97 F5D1 0063 B188 E2B6 95BD 4743
uid [ expired] DEB.SURY.ORG Automatic Signing Key <[email protected]>
pub rsa4096 2013-08-17 [SC] [expired: 2021-08-15]
75DD C3C4 A499 F1A1 8CB5 F3C8 CBF8 D6FD 518E 17E1
uid [ expired] Jessie Stable Release Key <[email protected]>
因此,我尝试了以下命令:
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys A4A9406876FCBD3C456770C88C718D3B5072E1F5
结果:
Executing: /tmp/apt-key-gpghome.8n1JFs3V5i/gpg.1.sh --keyserver keyserver.ubuntu.com --recv-keys A4A9406876FCBD3C456770C88C718D3B5072E1F5
gpg: failed to start the dirmngr '/usr/bin/dirmngr': No such file or directory
gpg: connecting dirmngr at '/tmp/apt-key-gpghome.8n1JFs3V5i/S.dirmngr' failed: No such file or directory
gpg: keyserver receive failed: No dirmngr
因此,我完成了以下内容,我做了以下内容:
sudo apt install dirmngr --install-recommends
结果:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
dbus-user-session libpam-systemd pinentry-gnome3 tor
The following NEW packages will be installed:
dirmngr
0 upgraded, 1 newly installed, 0 to remove and 10 not upgraded.
2 not fully installed or removed.
Need to get 597 kB of archives.
After this operation, 1,114 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian stretch/main amd64 dirmngr amd64 2.1.18-8~deb9u4 [597 kB]
Fetched 597 kB in 0s (7,412 kB/s)
Selecting previously unselected package dirmngr.
(Reading database ... 68920 files and directories currently installed.)
Preparing to unpack .../dirmngr_2.1.18-8~deb9u4_amd64.deb ...
Unpacking dirmngr (2.1.18-8~deb9u4) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up dirmngr (2.1.18-8~deb9u4) ...
Setting up google-fluentd (1.8.7-1) ...
Conffile /etc/google-fluentd/google-fluentd.conf has been modified. Remain untouched.
Conffile /etc/google-fluentd/baseline/google-fluentd.conf has been modified. Remain untouched.
Job for google-fluentd.service failed because the control process exited with error code.
See "systemctl status google-fluentd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript google-fluentd, action "start" failed.
● google-fluentd.service - LSB: data collector for Treasure Data
Loaded: loaded (/etc/init.d/google-fluentd; generated; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2022-04-21 16:26:02 UTC; 9ms ago
Docs: man:systemd-sysv-generator(8)
Process: 21302 ExecStart=/etc/init.d/google-fluentd start (code=exited, status=1/FAILURE)
Apr 21 16:26:02 marketing-vm systemd[1]: Starting LSB: data collector for Treasure Data...
Apr 21 16:26:02 marketing-vm google-fluentd[21302]: Starting google-fluentd 1.8.7: Disabled via metadata ... (warning).
Apr 21 16:26:02 marketing-vm google-fluentd[21302]: google-fluentd ... failed!
Apr 21 16:26:02 marketing-vm systemd[1]: google-fluentd.service: Control process exited, code=exited status=1
Apr 21 16:26:02 marketing-vm systemd[1]: Failed to start LSB: data collector for Treasure Data.
Apr 21 16:26:02 marketing-vm systemd[1]: google-fluentd.service: Unit entered failed state.
Apr 21 16:26:02 marketing-vm systemd[1]: google-fluentd.service: Failed with result 'exit-code'.
dpkg: error processing package google-fluentd (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of google-fluentd-catch-all-config:
google-fluentd-catch-all-config depends on google-fluentd (>= 1.3.0); however:
Package google-fluentd is not configured yet.
dpkg: error processing package google-fluentd-catch-all-config (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
google-fluentd
google-fluentd-catch-all-config
E: Sub-process /usr/bin/dpkg returned an error code (1)
我在研究之后和结果之后运行以下命令:
admin@marketing-vm:~$ systemctl status google-fluentd.service
Failed to connect to bus: No such file or directory
如何返回错误,但似乎已成功安装了Dirmngr,我认为这与Google Cloud Server有关,并且对此进行了研究。但是,如果您知道我该怎么做,我将不胜感激。但是让我们继续,因为这不是我的主要问题 然后,我再次尝试了以下命令
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys A4A9406876FCBD3C456770C88C718D3B5072E1F5
结果:
Executing: /tmp/apt-key-gpghome.q3eZMOsbBP/gpg.1.sh --keyserver keyserver.ubuntu.com --recv-keys A4A9406876FCBD3C456770C88C718D3B5072E1F5
gpg: key 8C718D3B5072E1F5: 4 duplicate signatures removed
gpg: key 8C718D3B5072E1F5: 60 signatures not checked due to missing keys
gpg: key 8C718D3B5072E1F5: "MySQL Release Engineering <[email protected]>" 33 new signatures
gpg: Total number processed: 1
gpg: new signatures: 33
和
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 15058500A0235D97F5D10063B188E2B695BD4743
结果:
Executing: /tmp/apt-key-gpghome.NYzCNLi5bV/gpg.1.sh --keyserver keyserver.ubuntu.com --recv-keys 15058500A0235D97F5D10063B188E2B695BD4743
gpg: key B188E2B695BD4743: 1 signature not checked due to a missing key
gpg: key B188E2B695BD4743: "DEB.SURY.ORG Automatic Signing Key <[email protected]>" 3 new signatures
gpg: Total number processed: 1
gpg: new signatures: 3
结果
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 75DDC3C4A499F1A18CB5F3C8CBF8D6FD518E17E1
:
Executing: /tmp/apt-key-gpghome.shHWXIw0ob/gpg.1.sh --keyserver keyserver.ubuntu.com --recv-keys 75DDC3C4A499F1A18CB5F3C8CBF8D6FD518E17E1
gpg: key CBF8D6FD518E17E1: 12 signatures not checked due to missing keys
gpg: key CBF8D6FD518E17E1: "Jessie Stable Release Key <[email protected]>" 10 new signatures
gpg: Total number processed: 1
gpg: new signatures: 10
然后,当我运行 sudo apt Update
时,我刚刚看到一个剩下的签名问题:
Hit:1 http://packages.cloud.google.com/apt google-cloud-monitoring-stretch-all InRelease
Ign:2 http://deb.debian.org/debian stretch InRelease
Hit:3 http://deb.debian.org/debian stretch-updates InRelease
Hit:4 http://deb.debian.org/debian stretch-backports InRelease
Hit:5 http://security.debian.org stretch/updates InRelease
Hit:6 http://packages.cloud.google.com/apt cloud-sdk-stretch InRelease
Hit:7 http://packages.cloud.google.com/apt google-compute-engine-stretch-stable InRelease
Hit:8 http://repo.mysql.com/apt/debian stretch InRelease
Hit:9 http://packages.cloud.google.com/apt google-cloud-packages-archive-keyring-stretch InRelease
Hit:10 http://deb.debian.org/debian stretch Release
Hit:11 https://packages.cloud.google.com/apt google-cloud-logging-stretch-all InRelease
Get:12 https://packages.sury.org/php stretch InRelease [6,839 B]
Err:8 http://repo.mysql.com/apt/debian stretch InRelease
The following signatures were invalid: EXPKEYSIG 8C718D3B5072E1F5 MySQL Release Engineering <[email protected]>
Get:14 https://packages.sury.org/php stretch/main amd64 Packages [356 kB]
Fetched 363 kB in 2s (149 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
26 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://repo.mysql.com/apt/debian stretch InRelease: The following signatures were invalid: EXPKEYSIG 8C718D3B5072E1F5 MySQL Release Engineering <[email protected]>
W: Failed to fetch http://repo.mysql.com/apt/debian/dists/stretch/InRelease The following signatures were invalid: EXPKEYSIG 8C718D3B5072E1F5 MySQL Release Engineering <[email protected]>
W: Some index files failed to download. They have been ignored, or old ones used instead.
也许我错了再次日志:
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 8C718D3B5072E1F5
结果:
gpg: key 8C718D3B5072E1F5: 4 duplicate signatures removed
gpg: key 8C718D3B5072E1F5: 60 signatures not checked due to missing keys
gpg: key 8C718D3B5072E1F5: "MySQL Release Engineering <[email protected]>" not changed
gpg: Total number processed: 1
gpg: unchanged: 1
因此我搜索了它,然后在以下文档上遵循说明:
https://dev.mysql.com/doc/refman/8.0/en/checking-gpg-signature.html
基于此处推荐的内容:
https://ubuntuforums.org/showthread.php
? :
sudo nano /home/admin/mysql_pubkey.asc
我复制并粘贴那里文档中提到的PGP公钥块。并保存了。 然后:
gpg --import /home/admin/mysql_pubkey.asc
结果:
gpg: /home/admin/.gnupg/trustdb.gpg: trustdb created
gpg: key 467B942D3A79BD29: public key "MySQL Release Engineering <mysql-build@os s.oracle.com>" imported
gpg: Total number processed: 1
gpg: imported: 1
然后我将公共密钥复制到txt文件,然后我做到了:
sudo apt-key add mysql_pubkey.txt
结果:
OK
我不知道为什么键467b942d3a79bd29与文档所说的是3A79BD29不同
。现在,当我运行 sudo apt-key列表
时,我会看到以下键:
/etc/apt/trusted.gpg
--------------------
pub rsa3072 2019-03-18 [SC] [expires: 2024-02-16]
1505 8500 A023 5D97 F5D1 0063 B188 E2B6 95BD 4743
uid [ unknown] DEB.SURY.ORG Automatic Signing Key <[email protected]>
sub rsa3072 2019-03-18 [E] [expires: 2024-02-16]
pub rsa4096 2021-12-14 [SC] [expires: 2023-12-14]
859B E8D7 C586 F538 430B 19C2 467B 942D 3A79 BD29
uid [ unknown] MySQL Release Engineering <[email protected]>
sub rsa4096 2021-12-14 [E] [expires: 2023-12-14]
/etc/apt/trusted.gpg.d/debian-archive-bullseye-automatic.gpg
------------------------------------------------------------
pub rsa4096 2021-01-17 [SC] [expires: 2029-01-15]
1F89 983E 0081 FDE0 18F3 CC96 73A4 F27B 8DD4 7936
uid [ unknown] Debian Archive Automatic Signing Key (11/bullseye) <[email protected]>
sub rsa4096 2021-01-17 [S] [expires: 2029-01-15]
/etc/apt/trusted.gpg.d/debian-archive-bullseye-security-automatic.gpg
---------------------------------------------------------------------
pub rsa4096 2021-01-17 [SC] [expires: 2029-01-15]
AC53 0D52 0F2F 3269 F5E9 8313 A484 4904 4AAD 5C5D
uid [ unknown] Debian Security Archive Automatic Signing Key (11/bullseye) <[email protected]>
sub rsa4096 2021-01-17 [S] [expires: 2029-01-15]
/etc/apt/trusted.gpg.d/debian-archive-bullseye-stable.gpg
---------------------------------------------------------
pub rsa4096 2021-02-13 [SC] [expires: 2029-02-11]
A428 5295 FC7B 1A81 6000 62A9 605C 66F0 0D6C 9793
uid [ unknown] Debian Stable Release Key (11/bullseye) <[email protected]>
/etc/apt/trusted.gpg.d/debian-archive-buster-automatic.gpg
----------------------------------------------------------
pub rsa4096 2019-04-14 [SC] [expires: 2027-04-12]
80D1 5823 B7FD 1561 F9F7 BCDD DC30 D7C2 3CBB ABEE
uid [ unknown] Debian Archive Automatic Signing Key (10/buster) <[email protected]>
sub rsa4096 2019-04-14 [S] [expires: 2027-04-12]
/etc/apt/trusted.gpg.d/debian-archive-buster-security-automatic.gpg
-------------------------------------------------------------------
pub rsa4096 2019-04-14 [SC] [expires: 2027-04-12]
5E61 B217 265D A980 7A23 C5FF 4DFA B270 CAA9 6DFA
uid [ unknown] Debian Security Archive Automatic Signing Key (10/buster) <[email protected]>
sub rsa4096 2019-04-14 [S] [expires: 2027-04-12]
/etc/apt/trusted.gpg.d/debian-archive-buster-stable.gpg
-------------------------------------------------------
pub rsa4096 2019-02-05 [SC] [expires: 2027-02-03]
6D33 866E DD8F FA41 C014 3AED DCC9 EFBF 77E1 1517
uid [ unknown] Debian Stable Release Key (10/buster) <[email protected]>
/etc/apt/trusted.gpg.d/debian-archive-jessie-automatic.gpg
----------------------------------------------------------
pub rsa4096 2014-11-21 [SC] [expires: 2022-11-19]
126C 0D24 BD8A 2942 CC7D F8AC 7638 D044 2B90 D010
uid [ unknown] Debian Archive Automatic Signing Key (8/jessie) <[email protected]>
/etc/apt/trusted.gpg.d/debian-archive-jessie-security-automatic.gpg
-------------------------------------------------------------------
pub rsa4096 2014-11-21 [SC] [expires: 2022-11-19]
D211 6914 1CEC D440 F2EB 8DDA 9D6D 8F6B C857 C906
uid [ unknown] Debian Security Archive Automatic Signing Key (8/jessie) <[email protected]>
/etc/apt/trusted.gpg.d/debian-archive-jessie-stable.gpg
-------------------------------------------------------
pub rsa4096 2013-08-17 [SC] [expired: 2021-08-15]
75DD C3C4 A499 F1A1 8CB5 F3C8 CBF8 D6FD 518E 17E1
uid [ expired] Jessie Stable Release Key <[email protected]>
/etc/apt/trusted.gpg.d/debian-archive-stretch-automatic.gpg
-----------------------------------------------------------
pub rsa4096 2017-05-22 [SC] [expires: 2025-05-20]
E1CF 20DD FFE4 B89E 8026 58F1 E0B1 1894 F66A EC98
uid [ unknown] Debian Archive Automatic Signing Key (9/stretch) <[email protected]>
sub rsa4096 2017-05-22 [S] [expires: 2025-05-20]
/etc/apt/trusted.gpg.d/debian-archive-stretch-security-automatic.gpg
--------------------------------------------------------------------
pub rsa4096 2017-05-22 [SC] [expires: 2025-05-20]
6ED6 F5CB 5FA6 FB2F 460A E88E EDA0 D238 8AE2 2BA9
uid [ unknown] Debian Security Archive Automatic Signing Key (9/stretch) <[email protected]>
sub rsa4096 2017-05-22 [S] [expires: 2025-05-20]
/etc/apt/trusted.gpg.d/debian-archive-stretch-stable.gpg
--------------------------------------------------------
pub rsa4096 2017-05-20 [SC] [expires: 2025-05-18]
067E 3C45 6BAE 240A CEE8 8F6F EF0F 382A 1A7B 6500
uid [ unknown] Debian Stable Release Key (9/stretch) <[email protected]>
/etc/apt/trusted.gpg.d/google-cloud-packages-archive-keyring.gpg
----------------------------------------------------------------
pub rsa2048 2021-03-01 [SC] [expires: 2023-03-02]
7F92 E05B 3109 3BEF 5A3C 2D38 FEEA 9169 307E A071
uid [ unknown] Rapture Automatic Signing Key (cloud-rapture-signing-key-2021-03-01-08_01_09.pub)
sub rsa2048 2021-03-01 [E]
pub rsa2048 2020-12-04 [SC] [expires: 2022-12-04]
59FE 0256 8272 69DC 8157 8F92 8B57 C5C2 836F 4BEB
uid [ unknown] gLinux Rapture Automatic Signing Key (//depot/google3/production/borg/cloud-rapture/keys/cloud-rapture-pubkeys/cloud-rapture-signing-key-2020-12-03-16_08_05.pub) <[email protected]>
sub rsa2048 2020-12-04 [E]
sudo apt apt update 时,我仍然会面临相同的
Hit:1 http://packages.cloud.google.com/apt google-cloud-monitoring-stretch-all InRelease
Ign:2 http://deb.debian.org/debian stretch InRelease
Hit:3 http://security.debian.org stretch/updates InRelease
Hit:4 http://packages.cloud.google.com/apt cloud-sdk-stretch InRelease
Hit:5 http://deb.debian.org/debian stretch-updates InRelease
Hit:6 http://packages.cloud.google.com/apt google-compute-engine-stretch-stable InRelease
Hit:7 http://deb.debian.org/debian stretch-backports InRelease
Hit:8 http://packages.cloud.google.com/apt google-cloud-packages-archive-keyring-stretch InRelease
Hit:9 http://deb.debian.org/debian stretch Release
Hit:10 http://repo.mysql.com/apt/debian stretch InRelease
Hit:11 https://packages.cloud.google.com/apt google-cloud-logging-stretch-all InRelease
Hit:12 https://packages.sury.org/php stretch InRelease
Err:10 http://repo.mysql.com/apt/debian stretch InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8C718D3B5072E1F5
Reading package lists... Done
Building dependency tree
Reading state information... Done
26 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://repo.mysql.com/apt/debian stretch InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8C718D3B5072E1F5
W: Failed to fetch http://repo.mysql.com/apt/debian/dists/stretch/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8C718D3B5072E1F5
W: Some index files failed to download. They have been ignored, or old ones used instead.
结果
gpg --delete-key 8C718D3B5072E1F5
。
gpg (GnuPG) 2.1.18; Copyright (C) 2017 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
gpg: key "8C718D3B5072E1F5" not found: Not found
gpg: 8C718D3B5072E1F5: delete key failed: Not found
运行
gpg --keyid-format=long --with-fingerprint --list-keys 8C718D3B5072E1F5
但是,当我 :
gpg: error reading key: No public key
如果您可以帮助我解决这个问题,我将不胜感激
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
通常,在添加软件包时,签名验证错误(和不受信任的签名)的原因是您已经用光了磁盘空间。这可能出于多种原因发生,例如在Docker和Docker VM磁盘(存储所有图像,图层和卷)下运行,或者
/tmp
已满(也许是因为它是在支持的文件系统)。释放磁盘空间,然后重试。请注意,如果在VM中运行,则必须释放VM可用的磁盘空间。释放主机上的磁盘空间不是一个完整的解决方案。对于Docker,请尝试
Docker System Prune -A
。Usually the cause of signature validation errors (and untrusted signatures) when adding packages is that you have run out of disk space. This can happen for a number of reasons, such as running under Docker and the Docker VM Disk (which stores all the images and layers and volumes) is full, or
/tmp
is full (perhaps because it is on a small, memory-backed file system).Free up disk space and try again. Note that if running in a VM, you must free up the disk space available to the VM. Freeing up disk space on the host is not a complete solution. For Docker, try
docker system prune -a
.