nik/liana
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge #221: just put the whole gpg key

Browse Source 
52341db41d719f7cbb224d9164593f5f2992eae7 just put the whole gpg key (Kevin Loaec)

Pull request description:

  I'm quite sure it does the check for you. So i also removed the extra comment. If i'm doing something wrong plz educate me :D

ACKs for top commit:
  darosior:
    I wouldn't be surprised if gpg was doing something surprising like transforming the key into a fingerprint before pulling from the keyserver. On the other hand it's the only bit of additional information re: checking GPG signatures in this document so being consistent is probably better. ACK 52341db41d719f7cbb224d9164593f5f2992eae7

Tree-SHA512: 95cadf5a6d93b63dbf7072cc61129feb2d5a229442ba6a4eaa6f741228d5404b929ba262b3550759edef230baa3aa09e469017362e37103de0a6eed5e4331a90
This commit is contained in:
Antoine Poinsot 2022-12-14 18:31:30 +01:00
commit 87fac3bcea
No known key found for this signature in database
GPG Key ID: E13FC145CD3F4304
1 changed files with 1 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
doc/BUILD.md
View File

@ -40,9 +40,8 @@ sub rsa4096/0x5CB4A9347B3B09DC 2014-12-15 [S]
You can therefore pull the key from either the above or from a keyserver:
```
$ gpg --keyserver hkps://keys.openpgp.org --receive 0x85AB96E6FA1BE5FE
$ gpg --keyserver hkps://keys.openpgp.org --receive 108F66205EAEB0AAA8DD5E1C85AB96E6FA1BE5FE
```
(Make sure to double check the whole key is the same, not just the fingerprint.)
And then you can download the archive corresponding to your system and CPU architecture, verify the
signature and use the `cargo` binary from this archive to build Liana. Here is an example for