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