키링을 다운로드하고 공개 키를 가져온 후에도 apt가 여전히 공개 키를 사용할 수 없는 이유는 무엇입니까?

brave-browser-beta설치 하려고 하는데데비안 테스트다음 스크립트를 실행하십시오 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확인되었습니다 . 왜 :에서 옵니까 ? 얼마 전 Ubuntu 22.04 LTS에서 동일한 문제가 발생했습니다. 성공적으로 설치할 수 있어요ls -l-rw------- 1 root root 2.5K Jan 27 13:01 /usr/share/keyrings/brave-browser-beta-archive-keyring.gpgaptGPG 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 0B31DBA06A8A26F9brave-browser-beta고물그러나 서명 키를 가져올 필요는 없습니다.