asc extension at the end - which is missing in Brave’s webpage and GitHub) in this example would be: brave-browser-nightly_1.40.57_
deb extension at the end) what I’m looking is for its signature file (. gpg -local-user 0B31DBA06A8A26F9 -output brave-browser-nightly_1.40.57_ -detach-sign brave-browser-nightly_1.40.57_bįor this installation file (. sig extensions at the end), for the benefit of Brave users to differentiate these installation files from potential fake ones.īrave Browser’s version: brave-browser-nightly_1.40.57_bĬould be signed by keyid 0B31DBA06A8A26F9, as this is the signing key Brave devs have assigned for their Nightly versions.įor this example, Brave devs could sign this installation file by using this command (i.e. The main purpose of those public keyid’s are for Brave devs to digitally sign each installation file with its corresponding secret keys in order to stamp them ‘as originals’ (and subsequently create a file for each with same name but adding. After visit that url, I inspected both signing keys, and deducted that Brave Release signing key has a public keyid: 0BB75829C2D4E821 Beta, Dev and Nightly signing key has a public keyid: 0B31DBA06A8A26F9
0 kommentar(er)
