Skip to content

Commit 5564877

Browse files
classabbyampthe-maldridge
authored andcommitted
installation/index: remove signify instructions
signify and minisign are no longer cross-compatible, and minisign is more cross-platform and will have some integrations into xbps, so it makes more sense to use minisign from now on. also update the instructions using the 20230628 images.
1 parent 7614d36 commit 5564877

File tree

1 file changed

+18
-37
lines changed

1 file changed

+18
-37
lines changed

src/installation/index.md

Lines changed: 18 additions & 37 deletions
Original file line numberDiff line numberDiff line change
@@ -63,23 +63,12 @@ This verifies that the image is not corrupt.
6363
Prior to using any image you're strongly encouraged to validate the signatures
6464
on the image to ensure they haven't been tampered with.
6565

66-
Current images are signed using a signify key that is specific to the release.
66+
Current images are signed using a minisign key that is specific to the release.
6767
If you're on Void already, you can obtain the keys from the `void-release-keys`
6868
package, which will be downloaded using your existing XBPS trust relationship
6969
with your mirror and package signatures. You will also need a copy of
70-
[signify(1)](https://man.voidlinux.org/signify.1) or
71-
[minisign(1)](https://man.voidlinux.org/minisign.1); on Void, these are provided
72-
by the `outils` or `minisign` packages, respectively.
73-
74-
To obtain `signify` when using a Linux distribution or operating system other
75-
than Void Linux:
76-
77-
- Install the `signify` package in Arch Linux and Arch-based distros.
78-
- Install the `signify-openbsd` package in Debian and Debian-based distros.
79-
- Install the package listed
80-
[here](https://repology.org/project/signify-openbsd/versions) for your
81-
distribution.
82-
- Install `signify-osx` with homebrew in macOS.
70+
[minisign(1)](https://man.voidlinux.org/minisign.1); on Void, this is provided
71+
by the `minisign` package.
8372

8473
The `minisign` executable is usually provided by a package of the same name, and
8574
can also be installed on Windows, even without WSL or MinGW.
@@ -92,44 +81,36 @@ Once you've obtained the key, you can verify your image with the `sha256sum.sig`
9281
and `sha256sum.txt` files. First, you need to verify the authenticity of the
9382
`sha256sum.txt` file.
9483

95-
The following examples demonstrate the verification of the `sha256sum.txt` file
96-
for the 20210930 images. Firstly, with `signify`:
84+
The following example demonstrates the verification of the `sha256sum.txt` file
85+
for the 20230628 images with `minisign`:
9786

9887
```
99-
$ signify -V -p /etc/signify/void-release-20210930.pub -x sha256sum.sig -m sha256sum.txt
100-
Signature Verified
101-
```
102-
103-
And secondly, with `minisign`:
104-
105-
```
106-
$ minisign -V -p /etc/signify/void-release-20210930.pub -x sha256sum.sig -m sha256sum.txt
88+
$ minisign -V -p /usr/share/void-release-keys/void-release-20230628.pub -x sha256sum.sig -m sha256sum.txt
10789
Signature and comment signature verified
108-
Trusted comment: timestamp:1634597366 file:sha256sum.txt
90+
Trusted comment: This key is only valid for images with date 20230628.
10991
```
11092

11193
Finally, you need to verify that the checksum for your image matches the one in
11294
the `sha256sum.txt` file. This can be done with the
113-
[sha256(1)](https://man.voidlinux.org/md5.1) utility, again from the `outils`
114-
package, as demonstrated below for the 20210930 `x86_64` image:
95+
[sha256(1)](https://man.voidlinux.org/md5.1) utility from the `outils` package,
96+
as demonstrated below for the 20230628 `x86_64` base image:
11597

11698
```
117-
$ sha256 -C sha256sum.txt void-live-x86_64-20210930.iso
118-
(SHA256) void-live-x86_64-20210930.iso: OK
99+
$ sha256 -C sha256sum.txt void-live-x86_64-20230628-base.iso
100+
(SHA256) void-live-x86_64-20230628-base.iso: OK
119101
```
120102

121-
Alternatively, if the `sha256` utility isn't available to you, you can compute
122-
the SHA256 hash of the file, e.g. using
123-
[sha256sum(1)](https://man.voidlinux.org/sha256sum.1), and compare it to the
124-
value contained in `sha256sum.txt`:
103+
Alternatively, if the `sha256` utility isn't available to you, you can use
104+
[sha256sum(1)](https://man.voidlinux.org/sha256sum.1):
125105

126106
```
127-
$ sha256sum void-live-x86_64-20210930.iso
128-
45b75651eb369484e1e63ba803a34e9fe8a13b24695d0bffaf4dfaac44783294 void-live-x86_64-20210930.iso
129-
$ grep void-live-x86_64-20210930.iso sha256sum.txt
130-
SHA256 (void-live-x86_64-20210930.iso) = 45b75651eb369484e1e63ba803a34e9fe8a13b24695d0bffaf4dfaac44783294
107+
$ sha256sum -c sha256sum.txt --ignore-missing
108+
void-live-x86_64-20230628-base.iso: OK
131109
```
132110

111+
If neither program is available to you, you can compute the SHA256 hash of the
112+
file and compare it to the value contained in `sha256sum.txt`.
113+
133114
If the verification process does not produce the expected "OK" status, do not
134115
use it! Please alert the Void Linux team of where you got the image and how you
135116
verified it, and we will follow up on it.

0 commit comments

Comments
 (0)