GPG Key mismatch on CentOS linux (release channel)

Unable to install release build (currently at 1.42.88-1) on CentOS (7.9.2009) release.

Followed the instructions for CentOS on website:

1. % sudo dnf install dnf-plugins-core
2. % sudo dnf config-manager --add-repo
3. % sudo rpm --import
4. % sudo dnf install brave-browser-nightly


Total download size: 95 M
Installed size: 95 M
Downloading Packages:
(1/2): brave-keyring-1.10-1.noarch.rpm                                                                                            33 kB/s |  11 kB     00:00    
(2/2): brave-browser-1.42.88-1.x86_64.rpm                                                                                        2.5 MB/s |  95 MB     00:37    
Total                                                                                                                            2.5 MB/s |  95 MB     00:37     
warning: /var/cache/dnf/brave-browser-rpm-release.s3.brave.com_x86_64_-d55d330619c02b48/packages/brave-browser-1.42.88-1.x86_64.rpm: Header V4 RSA/SHA512 Signature, key ID 82d3dc6c: NOKEY
Public key for brave-browser-1.42.88-1.x86_64.rpm is not installed
Public key for brave-keyring-1.10-1.noarch.rpm is not installed
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: GPG check FAILED

Key appear to be installed ok:

% sudo rpm -q gpg-pubkey --qf '%{NAME}-%{VERSION}-%{RELEASE}\t%{SUMMARY}\n'
gpg-pubkey-f4a80eb5-53a7ff4b	gpg(CentOS-7 Key (CentOS 7 Official Signing Key) <>)
gpg-pubkey-c2d4e821-6285304f	gpg(Brave Software <>)

And it seems to match the one at published on the website.

Does a newer key need to be uploaded for the release channel?

Note that I was able to install the nightly channel release without a problem.

Many thanks.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.