PackageTrack

Go modules · #2360

github.com/AlexSSD7/linsk

v0.2.2AlexSSD7/linsk ↗

Release timeline

13 releases since 2023
202420252026

Releases

  1. v0.2.3-0.20241101163109-4c98a8500c4e1 Nov 2024pre-release

    Nothing published for this version

  2. v0.2.3-0.20240617213212-5e86be6e721d17 Jun 2024pre-release

    Nothing published for this version

  3. v0.2.218 Nov 2023
    Release notes

    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>
    Open source →
  4. v0.2.2-0.20231118094804-21d1fd1469d418 Nov 2023pre-release

    Nothing published for this version

  5. v0.2.131 Oct 2023
    Release notes

    Changelog

    This is a minor maintenance release, predominantly containing the fix for compatibility issues for Intel-based macOS machines (darwin/amd64).

    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.1.txt.sig linsk_sha256_v0.2.1.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.1.txt) and compare the checksums. You can generate a checksum by executing this command:

    sha256sum <file path>
    Open source →
  6. v0.2.1-0.20231031152012-47e78c6ca5e331 Oct 2023pre-release

    Nothing published for this version

  7. v0.2.028 Sept 2023
    Release notes

    ⚠️ 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 <[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.0.txt) and compare the checksums. You can generate a checksum by executing this command:

    sha256sum <file path>
    Open source →
  8. v0.1.2-0.20230928102225-cf7889c5157a28 Sept 2023pre-release

    Nothing published for this version

  9. v0.1.2-0.20230927144426-02d3bd1aee4927 Sept 2023pre-release

    Nothing published for this version

  10. v0.1.111 Sept 2023
    Release notes

    ⚠️ Obsolete version

    This release is susceptible to the Faulty raw device block size detection serious bug.

    Linsk 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.

    More information: serious-bug-disclosures/README.md

    Changelog

    This is a minor maintenance release containing insignificant fixes following the initial release.

    The exact list of changes is as follows:

    • Enable qemu-system stderr passthrough when running with --vm-debug option.
    • Do not force-disable page cache for passed-through devices.
    • Fix linsk version showing v0.0.0.

    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.1.1.txt.sig linsk_sha256_v0.1.1.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.1.1.txt) and compare the checksums. You can generate a checksum by executing this command:

    sha256sum <file path>
    Open source →
  11. v0.1.1-0.20230911090515-e4b1fb627ea611 Sept 2023pre-release

    Nothing published for this version

  12. v0.1.1-0.20230904125714-ab292d72db204 Sept 2023pre-release

    Nothing published for this version

  13. v0.1.04 Sept 2023
    Release notes

    ⚠️ Obsolete version

    This release is susceptible to the Faulty raw device block size detection serious bug.

    Linsk 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.

    More information: serious-bug-disclosures/README.md

    Changelog

    This is the initial release of Linsk.

    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 the following:

    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.1.0.txt.sig linsk_sha256_v0.1.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 <[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.1.0.txt) and compare the checksums. You can generate a checksum by executing the following command:

    sha256sum <file path>
    Open source →