This release has the following changes:
In investigating issue #126, it was determined that when a filesystem is dismounted and other programs still have open files or directories on it, that these file handles were not being cleaned up. Also, if the encrypted files resided on a USB drive, then the USB drive could not be ejected after dismounting without exiting cppcryptfs. This release cleans up (closes) any such leftover file or directory handles after dismounting the filesystem. It also adds an option to prompt the user before dismounting a filesystem that still has open file or directory handles.
This release was built using Dokany 1.5.0.2000. It has been tested with Dokany 1.5.0.3000.
You will need to install or upgrade Dokany to 1.5.x.x.
https://github.com/dokan-dev/dokany/releases
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.
I've decided that the file sizes and hashes aren't needed because the executables are signed anyway. So I've stopped posting them with the releases.
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.