The following signatures couldn't be verified because the public key is not available: NO PUBKEY

1 개요

The following signatures couldn't be verified because the public key is not available: NO PUBKEY

2 문제 상황

# apt-get update
Hit:1 http://security.debian.org/debian-security buster/updates InRelease
Hit:2 http://deb.debian.org/debian buster InRelease
Hit:3 http://deb.debian.org/debian buster-updates InRelease
Hit:4 https://download.docker.com/linux/debian buster InRelease
Err:1 http://security.debian.org/debian-security buster/updates InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
...

# apt update
Get:1 https://cli.github.com/packages stable InRelease [3917 B]
Ign:1 https://cli.github.com/packages stable InRelease
Hit:2 http://archive.ubuntu.com/ubuntu focal InRelease
Hit:3 http://archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:4 http://security.ubuntu.com/ubuntu focal-security InRelease
Hit:5 http://archive.ubuntu.com/ubuntu focal-backports InRelease
Fetched 3917 B in 1s (3658 B/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
164 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: GPG error: https://cli.github.com/packages stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5

3 조치 방법

# without proxy
apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 40976EAF437D05B5 3B4FE6ACC0B21F32
# with proxy
apt-key adv --keyserver keyserver.ubuntu.com --keyserver-options "http-proxy=http://<proxy>:<port>" --recv-keys 40976EAF437D05B5 3B4FE6ACC0B21F32

실행 예시

root@wsl:~# apt-key adv --keyserver keyserver.ubuntu.com --keyserver-options "http-proxy=http://10.20.30.40:5060" --recv-keys 40976EAF437D05B5
Executing: /tmp/apt-key-gpghome.7ZLvshQ0A0/gpg.1.sh --keyserver keyserver.ubuntu.com --keyserver-options http-proxy=http://127.0.0.1:8080 --recv-keys 40976EAF437D05B5
gpg: key 40976EAF437D05B5: public key "GitHub CLI <opensource+cli@github.com>" imported
gpg: Total number processed: 1
gpg:               imported: 1

root@wsl:~# apt-key adv --keyserver keyserver.ubuntu.com --keyserver-options "http-proxy=http://10.20.30.40:5060" --recv-keys E80246AC9E13BDF5
Executing: /tmp/apt-key-gpghome.i5op4yxpUd/gpg.1.sh --keyserver keyserver.ubuntu.com --keyserver-options http-proxy=http://10.20.30.40:5060 --recv-keys E80246AC9E13BDF5
gpg: key 7913F58BD02B4691: 2 duplicate signatures removed
gpg: key 7913F58BD02B4691: "Google Inc. (Linux Packages Signing Authority) <linux-packages-keymaster@google.com>" 3 new signatures
gpg: key 7913F58BD02B4691: "Google Inc. (Linux Packages Signing Authority) <linux-packages-keymaster@google.com>" 2 new subkeys
gpg: Total number processed: 1
gpg:            new subkeys: 2

4 또 다른 문제

#  apt-get update
Ign:1 https://download.docker.com/linux/ubuntu focal InRelease
Err:2 https://download.docker.com/linux/ubuntu focal Release
  Certificate verification failed: The certificate is NOT trusted. The certificate chain uses insecure algorithm.  Could not handshake: Error in the certificate verification. [IP: 127.0.0.1 8080]
Hit:3 https://cli.github.com/packages stable InRelease
Hit:4 http://archive.ubuntu.com/ubuntu focal InRelease
Hit:5 http://security.ubuntu.com/ubuntu focal-security InRelease
Hit:6 http://archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:7 http://archive.ubuntu.com/ubuntu focal-backports InRelease
Reading package lists... Done
E: The repository 'https://download.docker.com/linux/ubuntu focal Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

5 같이 보기

• apt-key adv
• apt-get update
• Certificate verification failed: The certificate is NOT trusted. The certificate chain uses insecure algorithm.

6 참고

• https://chrisjean.com/fix-apt-get-update-the-following-signatures-couldnt-be-verified-because-the-public-key-is-not-available/