3838### Verifying images
3939
4040Each image release's directory contains two files used to verify the image(s)
41- you download. First, there is a ` sha256 .txt` file containing image checksums to
42- verify the integrity of the downloaded images. Second is the ` sha256 .sig` file,
41+ you download. First, there is a ` sha256sum .txt` file containing image checksums to
42+ verify the integrity of the downloaded images. Second is the ` sha256sum .sig` file,
4343used to verify the authenticity of the checksums.
4444
4545It is necessary to verify both the image's integrity and authenticity. It is,
@@ -48,12 +48,12 @@ therefore, recommended that you download both files.
4848#### Verifying image integrity
4949
5050You can verify the integrity of a downloaded file using
51- [ sha256sum(1)] ( https://man.voidlinux.org/sha256sum.1 ) with the ` sha256 .txt` file
51+ [ sha256sum(1)] ( https://man.voidlinux.org/sha256sum.1 ) with the ` sha256sum .txt` file
5252downloaded above. The following command will check the integrity of only the
5353image(s) you have downloaded:
5454
5555```
56- $ sha256sum -c --ignore-missing sha256 .txt
56+ $ sha256sum -c --ignore-missing sha256sum .txt
5757void-live-x86_64-musl-20170220.iso: OK
5858```
5959
@@ -89,12 +89,12 @@ If you are not currently using Void Linux, it will also be necessary to obtain
8989the appropriate signing key from our Git repository
9090[ here] ( https://github.com/void-linux/void-packages/tree/master/srcpkgs/void-release-keys/files/ ) .
9191
92- Once you've obtained the key, you can verify your image with the ` sha256 .sig`
92+ Once you've obtained the key, you can verify your image with the ` sha256sum .sig`
9393file. The following example demonstrates the verification of the GCP musl
9494filesystem from the 20191109 release:
9595
9696```
97- $ signify -C -p /etc/signify/void-release-20191109.pub -x sha256 .sig void-GCP-musl-PLATFORMFS-20191109.tar.xz
97+ $ signify -C -p /etc/signify/void-release-20191109.pub -x sha256sum .sig void-GCP-musl-PLATFORMFS-20191109.tar.xz
9898Signature Verified
9999void-GCP-musl-PLATFORMFS-20191109.tar.xz: OK
100100```
@@ -103,13 +103,13 @@ If the verification process does not produce the expected "OK" status, do not
103103use it! Please alert the Void Linux team of where you got the image and how you
104104verified it, and we will follow up on it.
105105
106- For verification with ` minisign ` , it is necessary to rename the ` sha256 .sig`
107- file to ` sha256 .txt.minisig` and remove the first line from the ` .pub ` release
108- key. The following example demonstrates the verification of the ` sha256 .txt`
106+ For verification with ` minisign ` , it is necessary to rename the ` sha256sum .sig`
107+ file to ` sha256sum .txt.minisig` and remove the first line from the ` .pub ` release
108+ key. The following example demonstrates the verification of the ` sha256sum .txt`
109109file from the 20191109 release:
110110
111111```
112- $ minisign -Vm sha256 .txt -f -p void-release-20191109.pub
112+ $ minisign -Vm sha256sum .txt -f -p void-release-20191109.pub
113113void-release-20191109.pub: Success
114114```
115115
0 commit comments