Skip to content

Commit d397afa

Browse files
committed
chore: update readme to use relays 0.4.0
1 parent 6a109a8 commit d397afa

File tree

1 file changed

+18
-17
lines changed

1 file changed

+18
-17
lines changed

README.md

Lines changed: 18 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -35,55 +35,55 @@ Before running the binaries, you should first verify their authenticity. This wi
3535

3636
#### Arch
3737

38-
```sh
38+
```bash
3939
sudo pacman -S gnupg
4040
```
4141

4242
#### Debian/Ubuntu
4343

44-
```sh
44+
```bash
4545
sudo apt install -y gnupg
4646
```
4747

4848
### curl
4949

5050
#### Arch
5151

52-
```sh
52+
```bash
5353
sudo pacman -S curl
5454
```
5555

5656
#### Debian/Ubuntu
5757

58-
```sh
58+
```bash
5959
sudo apt install -y curl
6060
```
6161

6262
Now you need to import the public key that signed the manifest file which you can do by running the following command:
6363

64-
```sh
64+
```bash
6565
curl https://keybase.io/nodetec/pgp_keys.asc | gpg --import
6666
```
6767

6868
You're now ready to verify the manifest file. You will need to have the `relays-x.x.x-manifest.sha512sum` and the `relays-x.x.x-manifest.sha512sum.asc` files in the same directory as the binaries you downloaded where the `x.x.x` is replaced by whatever version of `relays` you're verifying.
6969

7070
To verify the manifest file run the following command:
7171

72-
```sh
72+
```bash
7373
gpg --verify relays-x.x.x-manifest.sha512sum.asc
7474
```
7575

7676
Here's the command to run for the latest version of `relays`:
7777

78-
```sh
79-
gpg --verify relays-0.3.0-manifest.sha512sum.asc
78+
```bash
79+
gpg --verify relays-0.4.0-manifest.sha512sum.asc
8080
```
8181

8282
You should see output similar to the following if the verification was successful:
8383

84-
```sh
85-
gpg: assuming signed data in 'relays-0.3.0-manifest.sha512sum'
86-
gpg: Signature made Thu 03 Oct 2024 01:29:21 PM UTC
84+
```bash
85+
gpg: assuming signed data in 'relays-0.4.0-manifest.sha512sum'
86+
gpg: Signature made Sat 05 Oct 2024 08:43:11 AM UTC
8787
gpg: using RSA key 252F57B9DCD920EBF14E6151A8841CC4D10CC288
8888
gpg: Good signature from "NODE-TEC Devs <[email protected]>" [unknown]
8989
gpg: aka "[jpeg image of size 5143]" [unknown]
@@ -93,7 +93,7 @@ Primary key fingerprint: 04BD 8C20 598F A5FD DE19 BECD 8F24 69F7 1314 FAD7
9393

9494
> Unless you tell GnuPG to trust the key, you'll see a warning similar to the following:
9595
96-
```sh
96+
```bash
9797
gpg: WARNING: This key is not certified with a trusted signature!
9898
gpg: There is no indication that the signature belongs to the owner.
9999
```
@@ -106,24 +106,25 @@ You have now verified the signature of the manifest file which ensures the integ
106106

107107
To verify the binaries you'll need to recompute the SHA512 hashes of the files, compare them with the corresponding hashes in the manifest file, and ensure they match exactly which you can do by running the following command:
108108

109-
```sh
109+
```bash
110110
sha512sum --check relays-x.x.x-manifest.sha512sum
111111
```
112112

113113
Here's the command to run for the latest version of `relays`:
114114

115-
```sh
116-
sha512sum --check relays-0.3.0-manifest.sha512sum
115+
```bash
116+
sha512sum --check relays-0.4.0-manifest.sha512sum
117117
```
118118

119119
If the verification was successful you should see the output similar to the following:
120120

121-
```sh
121+
```bash
122122
khatru-pyramid-0.1.0-x86_64-linux-gnu.tar.gz: OK
123+
nostr-rs-relay-0.9.0-x86_64-linux-gnu.tar.gz: OK
123124
strfry-1.0.1-x86_64-linux-gnu.tar.gz: OK
125+
wot-relay-0.1.12-x86_64-linux-gnu.tar.gz: OK
124126
relay29-0.4.0-khatru29-x86_64-linux-gnu.tar.gz: OK
125127
relay29-0.4.0-strfry29-x86_64-linux-gnu.tar.gz: OK
126-
wot-relay-0.1.12-x86_64-linux-gnu.tar.gz: OK
127128
```
128129

129130
By completing the above steps you will have successfully verified the integrity of the binaries.

0 commit comments

Comments
 (0)