Skip to content

v0.2.0 Release

Choose a tag to compare

View all tags
@AlexSSD7 AlexSSD7 released this 28 Sep 10:25
· 21 commits to master since this release
v0.2.0
cf7889c

鈿狅笍 Serious bug disclosure

Linsk v0.2.0 addresses the Faulty raw device block size detection serious bug. Versions below v0.2.0 are considered obsolete UNLESS:

  • The use of Linsk was limited exclusively to devices with a 512-byte logical block (sector) size, or
  • The experimental USB passthrough was used.

Please see serious-bug-disclosures/README.md@master for more information.

Changelog

The exact list of changes is as follows:

  • Implement raw device block size detection on Linsk's side. This addresses the Faulty raw device block size detection serious bug. This also improves the performance on devices with a block size of more than 512 bytes.
  • Remove the need to explicitly specify the file system in linsk run.
  • Optional VM mount device specification in linsk run. Falls back to the default of vdb (the entire drive) if none is specified.
  • Implement the support for LUKS containers (primarily with LVM and a volume group inside) via the --luks-container flag.

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.0.txt.sig linsk_sha256_v0.2.0.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 <alexandersadovskyi7@protonmail.com>" [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.0.txt) and compare the checksums. You can generate a checksum by executing this command:

sha256sum <file path>
Assets 7
Loading