-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Publish code signing keys and signatures for Linux #837
Comments
marking this for releasable builds since we already publish the linux signing keys on the website as mentioned to @mbacchi and @RyanJarv we will need to rotate the keys for brave-core since they are inadequately secure. we will then need to publish the new keys before release. https://brave.com/signing-keys |
I've supplied Sampson with the public signing key for our Linux builds. MacOS and Windows builds ongoing. |
This is waiting until closer to release date, but as far as I understand everything is ready to go. |
@jonathansampson has this on staging server for Linux so I'm going to close this issue. I posted this issue for Windows and macOS though: If we get it today too that's great and we can close it too, but tracking it in 1.x in the meantime. |
Is there any plan to sign git tags? |
Carried over from brave/browser-laptop#197
Our current status (browser-laptop):
On browser-laptop, end users can check the signature on the installer / binaries:
spctl --assess --verbose /Applications/Brave.app/
. If app is signed, it should return something like this:The digital signature is OK
The text was updated successfully, but these errors were encountered: