From 9f3e6ba0497b7ae85570747135008df400b036cb Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 11 Jun 2026 15:22:14 +0000 Subject: [PATCH] fix(install): use Brave Beta's own keyring (not the stable one) 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 --- install/lib/packages.sh | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/install/lib/packages.sh b/install/lib/packages.sh index 37d278c..012dfb2 100644 --- a/install/lib/packages.sh +++ b/install/lib/packages.sh @@ -45,10 +45,11 @@ install_brave_beta() { info "Brave Beta already installed" return fi - # All Brave channels share one signing key, hosted in the release bucket. - # The repo URL itself is still the beta bucket. + # Brave's Beta channel is signed with its own key (C3DE1DD4F661CDCB), + # NOT the stable keyring — the keyring file in the beta bucket includes + # "beta" in the name. 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" apt_update_once apt_install brave-browser-beta