☰

下载密钥环并导入公钥后，为什么 apt 仍无法使用公钥？

tag-icon • tag-icon apt gpg key-authentication
下载密钥环并导入公钥后，为什么 apt 仍无法使用公钥？

我正在尝试brave-browser-beta安装Debian 测试使用以下脚本运行root：

#!/bin/bash

pdir=$(dirname "${BASH_SOURCE[0]}")
skf="${pdir}/brave-beta-signing-key"

gpg --import "$skf"
  

brave-beta() {
  curl -fsSLo /usr/share/keyrings/brave-browser-beta-archive-keyring.gpg https://brave-browser-apt-beta.s3.brave.com/brave-browser-beta-archive-keyring.gpg
  echo "deb [signed-by=/usr/share/keyrings/brave-browser-beta-archive-keyring.gpg] https://brave-browser-apt-beta.s3.brave.com/ stable main">/etc/apt/sources.list.d/brave-browser-beta.list
  apt update && apt install -y brave-browser-beta
}      

brave-beta

其中brave-beta-signing-key包含从以下位置复制并粘贴的公钥的文件勇敢网。该脚本仅执行以下操作：按照官方说明安装浏览器。我得到以下输出：

gpg: key 0B31DBA06A8A26F9: public key "Brave Software (Brave Core Nightly Key) (We're reinventing the browser as a user-first platform for speed and privacy.) <[email protected]>" imported
gpg: Total number processed: 1
gpg:               imported: 1

Hit:1 http://deb.debian.org/debian trixie InRelease
Hit:2 http://security.debian.org/debian-security trixie-security InRelease     
Hit:3 http://deb.debian.org/debian trixie-updates InRelease                    
Get:4 https://brave-browser-apt-beta.s3.brave.com stable InRelease [7547 B]    
Err:4 https://brave-browser-apt-beta.s3.brave.com stable InRelease    
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0B31DBA06A8A26F9
Reading package lists... Done
W: GPG error: https://brave-browser-apt-beta.s3.brave.com stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0B31DBA06A8A26F9
E: The repository 'https://brave-browser-apt-beta.s3.brave.com stable InRelease' is not signed.
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.

这个调查我做过的包括m̀an apt-secure：

   The chain of trust in Debian starts (e.g.) when a maintainer uploads a
   new package or a new version of a package to the Debian archive. In
   order to become effective, this upload needs to be signed by a key
   contained in one of the Debian package maintainer keyrings (available
   in the debian-keyring package). Maintainers' keys are signed by other
   maintainers following pre-established procedures to ensure the identity
   of the key holder. Similar procedures exist in all Debian-based
   distributions.

我有debian-archive-keyring， 但不是debian-keyring预安装。然后我就安装了，debian-keyring 但是没有效果。我已导入完全相同的密钥，并已获得所需的密钥环，经/usr/share/keyrings/brave-browser-beta-archive-keyring.gpg, 确认ls -l。 -rw------- 1 root root 2.5K Jan 27 13:01 /usr/share/keyrings/brave-browser-beta-archive-keyring.gpg为什么我会从apt:得到GPG error: https://brave-browser-apt-beta.s3.brave.com stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0B31DBA06A8A26F9？前段时间我在 Ubuntu 22.04 LTS 上遇到了同样的问题。我可以成功brave-browser-beta安装安蒂克斯不过，无需导入签名密钥。

答案1

我无法安装brave-browser，也brave-browser-beta只能在一台我知道网卡有故障的笔记本电脑上安装，因为我前段时间在这里描述过。我的其他计算机上不存在该问题。

相关内容