EncFS GUI should create config for case-insensitive file system on Windows.

[pb2004]

Currently when creating new config for encfs via gui in maingui.cpp function call is for case-sensitive file system:
nameIOIface = BlockNameIO::CurrentInterface(); //

encfs4win/encfs/win/maingui.cpp

Line 279 in ad8367d

nameIOIface = BlockNameIO::CurrentInterface();

and

encfs4win/encfs/win/maingui.cpp

Line 296 in ad8367d

nameIOIface = BlockNameIO::CurrentInterface();

For case-insensitive fs these 2 lines should call BlockNameIO::CurrentInterface() with true:
nameIOIface = BlockNameIO::CurrentInterface(true);

To Reproduce
Create new encfs dir with gui.

Expected behavior
Case-insensitive file names in encfs encrypted folder.

Desktop (please complete the following information):

• OS: Windows 10
• Encfs4win version: v1.10.1
• Dokan version: v1.2.2.1000

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[jetwhiz]

Thanks for the report, @pb2004 !

I think you're right, this should be the same as when run via command line:

encfs4win/encfs/FileUtils.cpp

Lines 1027 to 1031 in ad8367d

	#if defined(__APPLE__) || defined(WIN32)
	nameIOIface = BlockNameIO::CurrentInterface(true);
	#else
	nameIOIface = BlockNameIO::CurrentInterface();
	#endif

Can you test out that change and confirm it fixes the issue on your end? You can also open a PR if you're interested in helping out!

[pb2004]

Thanks for the report, @pb2004 !

I think you're right, this should be the same as when run via command line:

encfs4win/encfs/FileUtils.cpp

Lines 1027 to 1031 in ad8367d

	#if defined(__APPLE__) || defined(WIN32)
	nameIOIface = BlockNameIO::CurrentInterface(true);
	#else
	nameIOIface = BlockNameIO::CurrentInterface();
	#endif

Can you test out that change and confirm it fixes the issue on your end? You can also open a PR if you're interested in helping out!

This change fixes the reported problem. Thanks.

[jetwhiz]

Thanks for the confirmation, @pb2004 ! We'll include this fix in the next release

[jetwhiz]

This is now fixed with v1.10.2 (via bd27fcc)