I’m just trying to confirm that the change is intentional, and I’d also like to know if we should now stop trusting the older key. (Perhaps you changed keys because it was compromised? Or did you just lose the old one? Because the key strength is the same so I’m not sure why you’d change keys.)
This change was indeed intentional. We added redundancy in order to continue to be able to sign new Linux binaries should the AWS HSM fail. Unfortunately, it was not possible to turn an existing key into a multi-region key. So both keys are okay and neither is compromised.
If you are using our official packages, then you shouldn’t have to change anything since the brave-keyring package will handle key rotations automatically for you. If you are verifying packages manually, then you can safely keep both keys in your keyring.
Thank you for the explanation! I am on a distro that you don’t release packages for so I’ve made my own GPG verification and installation script to upgrade Brave.
Void Linux! It’s not based on any other distro, rolling but very stable, runit instead of systemd, top rated in distrowatch, and packaging AFAIK is easily done, e.g this way for Firefox. Brave installed from the zipfile runs awesomely on it.