1.4.4

The signing key can be retrieved with below command:

gpg --recv-keys 0x6855E493B5B2DF96E319BB6D16E2E1ACC6F51242

CHANGELOG:

    [WINDOWS]
-- Add support for storing keys securely on Windows by using Window's Data Protection API.

    [LINUX][FSCRYPT]
-- Fix a bug that causes fscrypt folders paths that contain a space character from showing
    up in the GUI.
-- Prevent fscrypt error when creating a new volume with an already taken protector name
    by making sure we are using a unique protector name.
-- Add a GUI option to set protector's name  when creating fscrypt volume.
-- Add a GUI option to choose between using a custom passphrase,login passphrase or 
   a key file when creating fscrypt volume.
-- Add support for fscrypt keyfile.

    [ALL][ENCFS]
-- Fix a bug with encfs < 1.9.5 when used with custom config path location. SiriKali 
    will now pass the path through enviromental variable instead of
    using --config CLI option.

    [ALL][SECUREFS]
-- Add support for securefs key file(introduced in securefs version 0.11.1).

    [ALL]
-- Rework UI and move key management feature from settings windows to favorites window.

1.4.3

The signing key can be retrieved with below command:

gpg --recv-keys 0x6855E493B5B2DF96E319BB6D16E2E1ACC6F51242

Changelog
-- Add ability to set arbitrary folder paths to monitor for mount events.
-- Add ability to monitor gvfs mount events.
-- Fix a bug that prevented unlocking volumes with a path that contains "," character. 
    The bug was due to fuse using the character as an option separator.
-- Fix a bug that prevented recent versions of unlocked securefs from showing up
    in the GUI in MACOS.
-- Add a GUI option to "allow replaced file system" when creating/unlocking CryFS volume.
-- Set the option "--allow-replaced-filesystem" by default when creating a CryFS volume.
-- When dealing with CryFs volume in windows, do not support paths that are not in drive C
    to work around this bug: https://github.com/cryfs/cryfs/issues/319
-- Fix a breaking change in how fscrypt 0.2.7 reported its version info.

1.4.2

-- Assume passwords are utf8 encoded instead of latin-1. This is a breaking change 
   for those who were using a password that was not a valid latin-1 password.
-- Fix a crash on windows when an sshfs favorite entry is created with a remote 
   folder path of just ":/", example is a remote address of "abc@example:/".
-- Add a visible option to choose between creating a local drive or a network drive 
   when connecting to ssh server on windows.
-- Inforce a requirenment that says Sshfs-win should be atleast version 3.4.0.
-- Add support for "lock" command in fscrypt backend. This option is used for
   locking directories that use V2 encryption policies.

1.4.1

-- Add support for fscrypt backend. This backend will allow encrypting individual
   folders that reside in a file system that supports native encryption like ext4. 
   More info about this backend is here: https://github.com/google/fscrypt
-- Fix a bug with sshfs backend introduced in 1.4.0.
-- Various changes and improvements.

Notes on Fscrypt
SiriKali locks fscrypt encrypted directories using "--drop-caches=false"
option. More explanation about this option is here[1]. It is strongly advised to
unmount a file system after locking an encrypted directory.

Currently, fscrypt does not lock an unlocked directory but locks a file system that
hosts the unlocked directory. A recently locked directory on a file system that was not
umounted after the locking took place will probably leak a good amount of folder
content and this is why it is strongly advised to unmount a file system after a directory
is locked.

Fscrypt will work "as expected" when this[2] pull request is accepted and the version
of the kernel in use is >= 5.4

[1] https://github.com/mhogomchungu/sirikali/issues/122#issuecomment-540980754

[2] https://github.com/google/fscrypt/pull/148

  Downloads, 
  -- Arch linux users can get the latest version from: 
      https://aur.archlinux.org/packages/sirikali/

  -- Gentoo users can get the latest version from: 
      https://git.holgersson.xyz/foss/holgersson-overlay

1.4.0

changelog:
-- Make it buildable again on Qt < 5.10.0(1.3.9 broke this promise because 
    it should be buildable in debian 8)
-- Add a config option to show favorites entries on the tray icon context menu 
    with an ability to mount/unmount volume from the menu.
-- Fix a bug that prevented favorite entries with cipher path that starts with a dot 
   from showing up in the GUI.
-- Add GUI options to enable HiDPI option to scale the GUI when running 
   in HiDPI displays.

  Downloads, 
  -- Arch linux users can get the latest version from: 
      https://aur.archlinux.org/packages/sirikali/

  -- Gentoo users can get the latest version from: 
      https://git.holgersson.xyz/foss/holgersson-overlay

1.3.9

-- Add ability to run a custom command on user specified time interval.
-- Add ability to set premount, postmount, preunmount and postunmount 
    commands to run per favorite entry.
-- Add support for creating and unlocking volumes using yubikey's
    challenge-response feature.
-- Add ability to run user created custom backends/extensions. 
    This feature make it possible to configure SiriKali
    to run any tool that deals with mounting file systems. 
    Documentation on how to create a custom backed is
    here: 
    https://github.com/mhogomchungu/sirikali/wiki/How-to-create-SiriKali-custom-backend
-- Fix an occassional crash that happens when creating an internal wallet 
    when an internal version of lxqt_wallet is in use.

1.3.8

-- Remove backend timeout of 20 seconds because cryfs >= 0.10.0 may 
    take a very long time to finish.
-- Show a warning that says working with cryfs >= 0.10.0 may take a very 
    long time when creating/unlocking cryfs volumes.
-- Improves a window that manages favorites.

1.3.7

-- Add support for gocryptfs "idle" option.
-- Add ability to set a favorite volume that does not need a password. Useful when
   connecting to ssh server with a private key that does not need a password or 
   when getting credentials from external tools like keepass.
-- Add a config option to auto unmount volumes on logout(specifically, when SiriKali 
    receive sighup or sigterm).
-- Add Russian translations.
-- Fix a bug that prevented mounting gocryptfs volumes on MACOS.
-- Translations now works on MACOS.
-- Add support for Cryfs backend on windows.
-- Add support for using a mount folder on windows
    (sshfs, encfs and cryfs supports both mount folders and drive letters)

1.3.6

changelog
-- Add ability to pass both fuse options and options specific to backends when unlocking a 
    volume.
     -- For example, this ability will allow passing "--allow-filesystem-upgrade" option to 
         cryfs backend when unlocking a cryfs volume to automatically upgrade the 
         volume's file system when necessary.
-- Add a GUI way to create and unlock gocryptfs and encfs volumes in reverse mode.
-- Fix a bug in windows that allowed more than once instance to run.
-- Create drive letters on Windows with a label equals to the name of the cipher folder when
    unlocking volumes.

1.3.5

Important: The archive is signed with a new key because the old one uses SHA1
and some distributions no longer supports it. The new SHA2 and can be
imported with the following command:

gpg --recv-keys 0x6855E493B5B2DF96E319BB6D16E2E1ACC6F51242

changelog:
-- Add "-DPOLKIT_SUPPORT=" compile time option to disable polkit support. 
    Suid root-less ecryptfs-simple backend will not work if this option is turned off.
-- Fix a bug on windows that prevented SiriKali from seeing 64 bit sshfs-win.
-- Add ability to edit favorites entries.
-- Fix a bug on windows when unlocking securefs volume with a custom config path.

Supported backends on Linux:
1. Encfs
2. Securefs
3. Gocryptfs
4. Cryfs
5. Sshfs
6. Ecryptfs

Supported backends on MACOS
1. Encfs
2. Cryfs
3. Gocryptfs
4. Securefs

Supported backends on Microsoft Windows
1. Encfs[1]
2. Securefs
3. Sshfs

[1] https://github.com/mhogomchungu/encfs/releases/tag/1.9.5