Skip to content

Releases: mhogomchungu/zuluCrypt

7.0.0

19 Aug 14:13
Compare
Choose a tag to compare
The signing key can be retrieved with below command:

    gpg --recv-keys 0x02FC64E8DEBF43A8

Changelog:-

   -- Make the project builable with Qt6, default is still Qt5.
   -- Fix a bug that caused a VeraCrypt password to not be used when unlocking using keyfiles.
   -- Fix a bug that prevented using a YubiKey.

6.2.0

19 Jun 13:22
Compare
Choose a tag to compare
-- Update French translations.
-- Fix a bug that caused existing favorite entries to accidentally be deleted 
    and new ones to not get saved.
-- Fix a bug that caused saved passwords in libsecret to not be visible.
-- Version 6.1.0 modernized favorites functionality and moved saved 
   password UI to the favorites window and changes in both places
    introduced above bugs.

6.1.0

21 May 17:43
Compare
Choose a tag to compare
changelog

-- Add a GUI way to set advanced LUKS2 options when creating a LUKS2 volume.
-- Add a GUI way to set advanced LUKS2 options when adding a key to a LUKS2 volume.
-- Various changes and improvements.

6.0.0

29 Jan 11:04
Compare
Choose a tag to compare
changelog:

-- Add ability to show used LUKS key slots and their properties in zuluCrypt-gui.
-- Fix a bug that caused zuluCrypt to not set user specified digest hash when 
    creating LUKS2 volumes.
-- Default to creating LUKS2 volumes if installed version of cryptsetup supports it.
-- Make it buildable again on some systems.

5.7.1

04 Feb 06:22
Compare
Choose a tag to compare
-- Use cryptsetup instead of zuluplay to unlock TrueCrypt volumes if installed
   version of cryptsetup >= 1.6.0(released on January 14,2013).
-- Use cryptsetup instead of zuluplay to unlock VeraCrypt volumes if installed
   version of cryptsetup >= 1.6.7(released on March 23, 2015).
-- The two changes above will hopefully solve long standing problems around
    unlocking TrueCrypt/VeraCrypt volumes that use preboot authentication.
-- Use cryptsetup by default instead of dislocker to unlock BitLocker volumes
   if installed version of cryptsetup >= 2.3.0(released on February 3,2020).
   Users of cryptsetup >= 2.3.0 who prefer to use dislocker to unlock
   BitLocker volumes  should create a text file at "/etc/zuluCrypt/dislocker".

5.7.0

01 Oct 17:21
Compare
Choose a tag to compare
changelog:

-- Fix a bug introduced in 5.6.0 that prevents unlocking PLAIN dm-crypt volume
    that use non default crypto options because the selection button in
    zuluCrypt-gui always disabled.
-- Update French translations.
-- Don't resolve loop device paths to their backing file if they are partitioned.
-- Fix a bug that prevented restoring a LUKS2 volume header.
-- Identify authenticated luks2 volumes as luks2+.
-- Add support for creating authenticated luks2 volumes(the support in Currently
    in zuluCrypt-cli only).
-- Default to using 512bit keys when creating LUKS volumes.

5.6.0

19 Aug 05:01
Compare
Choose a tag to compare
-- Add ability to create volume keys using YubiKey's challenge-response feature.
-- Add GUI options to clear dead mount points(these are unused mount folders 
    located at /run/media/private/$USER). CLI users should call CLI components 
    with "--clear-dead-mount-points"
-- Fix a race condition bug introduced in version 5.5.0 that prevented volumes 
    from getting mounted under certain circumstances.

    Below command can be used to import a public key that can be used to
    verify these archives:

    gpg --recv-keys 0x6855E493B5B2DF96E319BB6D16E2E1ACC6F51242

5.5.0

01 May 07:54
Compare
Choose a tag to compare
Changelog:
-- Add support for unlocking bitlocker volumes using 
    dislocker(https://github.com/mhogomchungu/dislocker)
-- Fix a build issue on some distributions.
-- Add ability to create a plain dm-crypt volume at the end of a 
    regular file(steganography).
-- Various fixes and improvements.


5.4.0

19 Nov 10:41
Compare
Choose a tag to compare
changelog
-- fix a bug that caused a wrong password to be used when creating a 
    TrueCrypt/VeraCrypt volume from zuluCrypt-gui. Easiest way to notice this was 
    that a just created volume could not be unlocked.
-- fix a build issue on some distributions.

5.3.0

01 Nov 00:26
Compare
Choose a tag to compare
changelog:

-- Fix a build time error when build with certain new compilers and a runtime 
   crush when build with other newer compilers.
-- Add more support for wayland sessions by not requiring GUI to run from root's 
   account to perform some operations.
-- Add support for creating LUKS2 volumes(libcryptsetup >=2.0.0 is required)
-- Add support for unlocking of TrueCrypt and VeraCrypt volumes without 
    mounting their file system.
        -- Unlocking of a TrueCrypt volume is done by command: 
                    zuluCrypt-cli -O -d /dev/sdXX -t tcrypt
        -- Unlocking of a VeraCrypt volume is done by command: 
                    zuluCrypt-cli -O -d /dev/sdXX -t vcrypt