brianpooe/dotfiles
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix(install): use Brave Beta's own keyring (not the stable one)

Browse source 
Brave's Beta channel is signed with its own key (C3DE1DD4F661CDCB).
The previous attempt to share the stable keyring failed at apt update
with NO_PUBKEY because the release bucket's keyring only contains the
stable channel's key.

The correct URL is the beta bucket itself with the channel-specific
filename: brave-browser-apt-beta.s3.brave.com/brave-browser-beta-archive-keyring.gpg
This commit is contained in:
Claude 2026-06-11 15:22:14 +00:00
parent ac38ceccbc
commit 9f3e6ba049
No known key found for this signature in database
1 changed files with 4 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
install/lib/packages.sh
View file

@ -45,10 +45,11 @@ install_brave_beta() {
info "Brave Beta already installed" info "Brave Beta already installed"
return return
fi fi
# All Brave channels share one signing key, hosted in the release bucket. # Brave's Beta channel is signed with its own key (C3DE1DD4F661CDCB),
# The repo URL itself is still the beta bucket. # NOT the stable keyring — the keyring file in the beta bucket includes
# "beta" in the name.
add_apt_repo brave-browser-beta \ add_apt_repo brave-browser-beta \
https://brave-browser-apt-release.s3.brave.com/brave-browser-archive-keyring.gpg \ https://brave-browser-apt-beta.s3.brave.com/brave-browser-beta-archive-keyring.gpg \
"deb [signed-by=$KEYRINGS_DIR/brave-browser-beta.gpg arch=amd64] https://brave-browser-apt-beta.s3.brave.com/ stable main" "deb [signed-by=$KEYRINGS_DIR/brave-browser-beta.gpg arch=amd64] https://brave-browser-apt-beta.s3.brave.com/ stable main"
apt_update_once apt_update_once
apt_install brave-browser-beta apt_install brave-browser-beta