While installing Brave on Debian I get these errors:
The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY A8580BDC82D3DC6C
W: GPG error: https://brave-browser-apt-release.s3.brave.com stable InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY A8580BDC82D3DC6C
E: The repository ‘https://brave-browser-apt-release.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.
How can this issue be reproduced?: Running “sudo apt update” during installation on Linux systems.
I had the same problem using Linux Mint. I received this message after downloading Brave from the “Brave” web site. The download from Flatpak didn’t have this issue as far as I can tell. I’m new to linux but would like to remove this from showing up on the terminal not to mention being sure Brave has downloaded properly.
Warning: GPG error: https://brave-browser-apt-release.s3.brave.com stable InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY A8580BDC82D3DC6C
Error: The repository ‘https://brave-browser-apt-release.s3.brave.com stable InRelease’ is not signed.
Here’s a link to Brave’s page for installing Brave on Linux:
A few comments:
FIRST, I’M SHOUTING - SPECIFICALLY AT WHOMEVER MAINTAINS THIS (AND OTHER) WEB PAGES:
!!!INCLUDE AN EXPLICIT DATE INDICATING WHEN A PAGE WAS UPDATED!!!
Okay, enough with the shouting, but omitting the date when a web page was updated is bad form, bad practice, and just wrong.
Informally, I keep notes about my installations. I installed Brave on a desktop and a laptop both running Debian 11 (Bullseye) about a year ago. My notes differ slightly but materially from what’s on the referenced Brave web page, but it’s possible the differences reflect what’s appropriate for Debian 12 (Bookworm).
Also note on Brave’s page: while a Snap installation (a variant of ‘Flatpak’) is supported, Brave recommends installing from the ‘official’ package repositories.
Thanks for the reply. However, the link you sent is the one I used last night that prompted the error message in my post. That’s why I went to the Flatpak package mgr in Mint next. BTW I’m not sure who you are complaining to about explicit dates. When I made my first post and this reply there was a date listed to the right of the posts not to mention a notation at the top right of each post indicating when the post was made.
Sorry I was unclear. Yes, ‘Brave Community’ comments are date-and-time-stamped. My complaint is directed to whomever updates Brave’s website pages. For example. the page I ‘oneboxed’ is undated. That’s why I’m cautious about providing the specific sequence of instructions that worked for me - a year ago - with instances of Debian 11. One or more of those instructions - valid a year ago - may have been deprecated.
With that caution, this is what worked for me installing Brave on Debian 11 a year ago:
echo deb [arch=amd64 signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg] https://brave-browser-apt-release.s3.brave.com/ stable main | sudo tee /etc/apt/sources.list.d/brave-browser-release.list
4 Install Brave Browser
Update your repository list to reflect the new repository changes