This release requires Dokany 2.0.x. It will not work with Dokany 1.x
https://github.com/dokan-dev/dokany/releases
This release implements the "deterministic names" feature of gocryptfs. When a filesystem is created using this feature, then diriv files are not needed for encrypted file names. However, an attacker could tell if two directories have the same file name in them.
Please see:
https://github.com/rfjakob/gocryptfs/blob/master/Documentation/MANPAGE.md#-deterministic-names
This release also fixes the inconsistency whereby which passwords could be specified on the command line but not read from stdin when mounting from the command line and could be only read from stdin but not specified on the command when creating a filesystem from the command line. Now both creating (--init) and mounting can use either the -p argument to get the password or read it from stdin.
There is no installation program for cppcryptfs. Just save it somewhere (could be on your deskstop) and run it from there.
The executables are signed by the developer and are for 32/64-bit Windows 7 and higher.
The 64-bit version (cppcryptfs.exe) requires 64-bit Windows. The 32-bit version (cppcryptfs32.exe) will run on either 32 or 64-bit Windows, but it is recommended to use the 64-bit version of cppcryptfs on 64-bit Windows.
You can rename the 32-bit version to cppcryptfs.exe after downloading it if you wish.
Encedo Limited have generously offered to co-sign the binaries using their EV (Extended Validation) code-signing certificate. This eliminates the Windows SmartScreen warnings that happened when the executables were signed using only my open source developer code-signing certificate.
The co-signed binaries are here now.