Skip to content
Compare
Choose a tag to compare

v1.11.0-beta.4

Pre-release
Pre-release

Note: This is a beta release -- we ask that you test to ensure everything works properly for your setup!

This version is based on the following software:

Fixed

  • Upgrade OpenSSL to latest version (v1.1.1n)
  • Re-target VS Toolset to v142

Known Issues

  • Symbolic links are not yet supported inside encfs container (FUSE support needed -- see dokan-dev/dokany#343)
  • Buggy behavior when encfs isn't mounted to a drive letter (e.g., Z:) (issue #51)
    • Reparse points cause Windows/Dokany to convert filenames to all uppercase (see Dokany-issue #293)
    • This same issue applies to directory symbolic links and directory junctions, so avoid using them with encfs for now!
  • UTF-8 filesystem encodings not handled correctly in encfs and encfsctl (issue #79, #92, #94)
    • Thai/CJK multi-byte encodings not supported (issue #55 and #94)
Compare
Choose a tag to compare

v1.11.0-beta.3

Pre-release
Pre-release

Note: This is a beta release -- we ask that you test to ensure everything works properly for your setup!

This version is based on the following software:

Fixed

  • Upgraded dependencies to latest versions

Known Issues

  • Need to switch to OpenSSL v1.1
  • Symbolic links are not yet supported inside encfs container (FUSE support needed -- see dokan-dev/dokany#343)
  • Buggy behavior when encfs isn't mounted to a drive letter (e.g., Z:) (issue #51)
    • Reparse points cause Windows/Dokany to convert filenames to all uppercase (see Dokany-issue #293)
    • This same issue applies to directory symbolic links and directory junctions, so avoid using them with encfs for now!
  • UTF-8 filesystem encodings not handled correctly in encfs and encfsctl (issue #79, #92, #94)
    • Thai/CJK multi-byte encodings not supported (issue #55 and #94)
Compare
Choose a tag to compare

v1.11.0-beta.2

Pre-release
Pre-release

Note: This is a beta release -- we ask that you test to ensure everything works properly for your setup!

This version is based on the following software:

Fixed

  • Issue "EncFS GUI should create config for case-insensitive file system on Windows. #135" fixed

Known Issues

  • Symbolic links are not yet supported inside encfs container (FUSE support needed -- see dokan-dev/dokany#343)
  • Buggy behavior when encfs isn't mounted to a drive letter (e.g., Z:) (issue #51)
    • Reparse points cause Windows/Dokany to convert filenames to all uppercase (see Dokany-issue #293)
    • This same issue applies to directory symbolic links and directory junctions, so avoid using them with encfs for now!
  • UTF-8 filesystem encodings not handled correctly in encfs and encfsctl (issue #79, #92, #94)
    • Thai/CJK multi-byte encodings not supported (issue #55 and #94)
Compare
Choose a tag to compare

This version is based on the following software:

Fixed

  • Issue "EncFS GUI should create config for case-insensitive file system on Windows. #135" fixed

Known Issues

  • Symbolic links are not yet supported inside encfs container (FUSE support needed -- see dokan-dev/dokany#343)
  • Buggy behavior when encfs isn't mounted to a drive letter (e.g., Z:) (issue #51)
    • Reparse points cause Windows/Dokany to convert filenames to all uppercase (see Dokany-issue #293)
    • This same issue applies to directory symbolic links and directory junctions, so avoid using them with encfs for now!
  • UTF-8 filesystem encodings not handled correctly in encfs and encfsctl (issue #79, #92, #94)
    • Thai/CJK multi-byte encodings not supported (issue #55 and #94)
Compare
Choose a tag to compare

v1.11.0-beta.1

Pre-release
Pre-release

Note: This is a beta release -- we ask that you test to ensure everything works properly for your setup!

This version is based on the following software:

Known Issues

  • Symbolic links are not yet supported inside encfs container (FUSE support needed -- see dokan-dev/dokany#343)
  • Buggy behavior when encfs isn't mounted to a drive letter (e.g., Z:) (issue #51)
    • Reparse points cause Windows/Dokany to convert filenames to all uppercase (see Dokany-issue #293)
    • This same issue applies to directory symbolic links and directory junctions, so avoid using them with encfs for now!
  • UTF-8 filesystem encodings not handled correctly in encfs and encfsctl (issue #79, #92, #94)
    • Thai/CJK multi-byte encodings not supported (issue #55 and #94)
Compare
Choose a tag to compare

This version is based on the following software:

Known Issues

  • Symbolic links are not yet supported inside encfs container (FUSE support needed -- see dokan-dev/dokany#343)
  • Buggy behavior when encfs isn't mounted to a drive letter (e.g., Z:) (issue #51)
    • Reparse points cause Windows/Dokany to convert filenames to all uppercase (see Dokany-issue #293)
    • This same issue applies to directory symbolic links and directory junctions, so avoid using them with encfs for now!
  • UTF-8 filesystem encodings not handled correctly in encfs and encfsctl (issue #79, #92, #94)
    • Thai/CJK multi-byte encodings not supported (issue #55 and #94)
Compare
Choose a tag to compare

v1.10.1-RC15

Pre-release
Pre-release

Note: This is normally stable, but we ask that you test to ensure everything works properly for your setup.

This version is based on the following software:

Fixed

  • Dokany fixed an issue upstream that would sometimes result in an immediate drive unmount after mounting

Known Issues

  • UTF-8 filesystem encodings not handled correctly in encfs and encfsctl (issue #79, #92, #94)
  • Symbolic links are not yet supported inside encfs container (FUSE support needed -- see dokan-dev/dokany#343)
  • Buggy behavior when encfs isn't mounted to a drive letter (e.g., Z:) (issue #51)
    • Reparse points cause Windows/Dokany to convert filenames to all uppercase (see Dokany-issue #293)
    • This same issue applies to directory symbolic links and directory junctions, so avoid using them with encfs for now!
  • Dokan legacy still experiences issue #80, where cut-paste a folder may result in data loss.
  • Thai/CJK multi-byte encodings not supported (issue #55 and #94)
Compare
Choose a tag to compare

v1.10.1-RC14

Pre-release
Pre-release

Note: This is normally stable, but we ask that you test to ensure everything works properly for your setup.

This version is based on the following software:

Fixed

  • Issue " Dokan has released an updated package #119" fixed
  • Issue "Feature request: Show encfs4win version and Dokan version in 'About' dialog #115" fixed

Known Issues

  • UTF-8 filesystem encodings not handled correctly in encfs and encfsctl (issue #79, #92, #94)
  • Symbolic links are not yet supported inside encfs container (FUSE support needed -- see dokan-dev/dokany#343)
  • Buggy behavior when encfs isn't mounted to a drive letter (e.g., Z:) (issue #51)
    • Reparse points cause Windows/Dokany to convert filenames to all uppercase (see Dokany-issue #293)
    • This same issue applies to directory symbolic links and directory junctions, so avoid using them with encfs for now!
  • Dokan legacy still experiences issue #80, where cut-paste a folder may result in data loss.
  • Thai/CJK multi-byte encodings not supported (issue #55 and #94)
Compare
Choose a tag to compare

v1.10.1-RC13

Pre-release
Pre-release

Note: This is normally stable, but we ask that you test to ensure everything works properly for your setup.

This version is based on the following software:

Fixed

  • Issue "Simplest install: dokanfuse1.dll not found #89" fixed
  • Issue "Cannot save Excel files to mounted encfs volume #93" fixed in modern Dokany
  • Issue "Don't restart computer without asking during installation #96" fixed

Known Issues

  • UTF-8 filesystem encodings not handled correctly in encfs and encfsctl (issue #79, #92, #94)
  • Symbolic links are not yet supported inside encfs container (FUSE support needed -- see dokan-dev/dokany#343)
  • Buggy behavior when encfs isn't mounted to a drive letter (e.g., Z:) (issue #51)
    • Reparse points cause Windows/Dokany to convert filenames to all uppercase (see Dokany-issue #293)
    • This same issue applies to directory symbolic links and directory junctions, so avoid using them with encfs for now!
  • Dokan legacy still experiences issue #80, where cut-paste a folder may result in data loss.
  • Thai/CJK multi-byte encodings not supported (issue #55 and #94)

Dokan Legacy vs. Dokany Modern

Dokan v0.7.4 (legacy) is based on the original, abandoned Dokan project with various bug fixes and modernizations. Dokany v1.x (modern) is a significant rewrite designed for improved support on newer operating systems (e.g., Windows 10).

The legacy version is provided for those who prefer to use the original code-base, though it is recommended that users choose the modern release since it is still being actively maintained.

Compare
Choose a tag to compare

v1.10.1-RC12

Pre-release
Pre-release

Note: This is normally stable, but we ask that you test to ensure everything works properly for your setup.

This version is based on the following software:

Fixed

  • Issue "Moving directory causes data loss #80" fixed for Dokany modern

Known Issues

  • UTF-8 filesystem encodings not handled correctly in encfsctl (issue #79)
  • Symbolic links are not yet supported inside encfs container (FUSE support needed -- see dokan-dev/dokany#343)
  • Buggy behavior when encfs isn't mounted to a drive letter (e.g., Z:) (issue #51)
    • Reparse points cause Windows/Dokany to convert filenames to all uppercase (see Dokany-issue #293)
    • This same issue applies to directory symbolic links and directory junctions, so avoid using them with encfs for now!
  • Dokan legacy still experiences issue #80, where cut-paste a folder may result in data loss.
  • CJK multibyte encodings not supported (issue #55)
  • Building encfs legacy will give macro redefinition warnings
    • Dokan legacy (v0.7.4) uses windows.h for STATUS_ codes, while we now build against ntstatus

Dokan Legacy vs. Dokany Modern

Dokan v0.7.4 (legacy) is based on the original, abandoned Dokan project with various bug fixes and modernizations. Dokany v1.0 (modern) is a significant rewrite designed for improved support on newer operating systems (e.g., Windows 10).

The legacy version is provided for those who prefer to use the original code-base, though it is recommended that users choose the modern release since it is still being actively maintained.