Changelog
This is a minor hotfix release that addresses the Windows compatibility issue introduced in Linsk v0.2.1.
Verifying the signature
Linsk binaries are packaged with a PGP signature to verify the authenticity of the builds. gpg is required to verify signatures like this. You can fetch and import the signing key by executing:
curl https://raw.githubusercontent.com/AlexSSD7/linsk/b59880e6c4e2875a926aeaa7a3b9704df04b33ba/keys/AlexSSD7.key | gpg --import
Once you have imported the key, you can run the following to verify the signature of the file with SHA-256 hashes:
gpg --verify linsk_sha256_v0.2.2.txt.sig linsk_sha256_v0.2.2.txt
You should then see something like this:
gpg: Signature made Mon 04 Sep 2023 09:44:18 AM BST
gpg: using RSA key F7231DFD3333A27F71D171383B627C597D3727BD
gpg: Good signature from "AlexSSD7 <[email protected]>" [ultimate]
Please ensure that the key ID is F7231DFD3333A27F71D171383B627C597D3727BD
After the signature is verified successfully, you may now open the hashes file (linsk_sha256_v0.2.2.txt) and compare the checksums. You can generate a checksum by executing this command:
sha256sum <file path>