cppcryptfs 1.4.4.5

This release is for fixing issue #191.

This release requires Dokany 2.2.x. It will not work with Dokany 1.x.

https://github.com/dokan-dev/dokany/releases

There is no installation program for cppcryptfs. Just save it somewhere (could be on your desktop) 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.

The binaries are signed with the developer's Open Source Developer code-signing certificate. Unfortunately, unless software signed with this type of certificate is really popular and downloaded a lot, Microsoft still treats it with suspicion and will probably throw up a warning dialog when you try to run it. If you click "More Info" and then "Run Anyway", it will run. This warning will not happen on subsequent runs.

cppcryptfs 1.4.4.4

There are no changes other than using a newer Dokany version (2.2.0.1000).

This release requires Dokany 2.2.x. It will not work with Dokany 1.x.

https://github.com/dokan-dev/dokany/releases

There is no installation program for cppcryptfs. Just save it somewhere (could be on your desktop) 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.

The binaries are signed with the developer's Open Source Developer code-signing certificate. Unfortunately, unless software signed with this type of certificate is really popular and downloaded a lot, Microsoft still treats it with suspicion and will probably throw up a warning dialog when you try to run it. If you click "More Info" and then "Run Anyway", it will run. This warning will not happen on subsequent runs.

cppcryptfs 1.4.4.3

There are no changes other than using a newer Dokany version (2.1.0.1000).

This release requires Dokany 2.1.x. It will not work with Dokany 1.x.

https://github.com/dokan-dev/dokany/releases

There is no installation program for cppcryptfs. Just save it somewhere (could be on your desktop) 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.

The binaries are signed with the developer's Open Source Developer code-signing certificate. Unfortunately, unless software signed with this type of certificate is really popular and downloaded a lot, Microsoft still treats it with suspicion and will probably throw up a warning dialog when you try to run it. If you click "More Info" and then "Run Anyway", it will run. This warning will not happen on subsequent runs.

cppcryptfs 1.4.4.2

This release requires Dokany 2.0.x. It will not work with Dokany 1.x

https://github.com/dokan-dev/dokany/releases

This release uses OpenSSL 3.0 LTS instead of OpenSSL 1.1 which is no longer supported.

There are no other changes.

There is no installation program for cppcryptfs. Just save it somewhere (could be on your desktop) 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.

The binaries are signed with the developer's Open Source Developer code-signing certificate. Unfortunately, unless software signed with this type of certificate is really popular and downloaded a lot, Microsoft still treats it with suspicion and will probably throw up a warning dialog when you try to run it. If you click "More Info" and then "Run Anyway", it will run. This warning will not happen on subsequent runs.