Null filename encryption shows/leaks .encfs6.xml file to encrypted disk

[vovcacik]

Environment

• Windows version: Windows 10 Pro
• Processor architecture: x64
• Encfs4win version: encfs version 1.10.1-RC10
• Dokan version (legacy, modern): Dokany 1.0.2

Description

When I choose not to encrypt filenames, the newly created encrypted disk will contain .encfs6.xml file from the beginning.

Expected behavior vs. actual behavior

Freshly created encrypted disk should be empty, but it already cointained the encfs config file.

Steps to reproduce problem

1. Just create encfs disk in expert mode, stay with the default values, but select Null filename encryption method.

Relevant logs

Nothing interesting in verbose log.

[jetwhiz]

Hi @vovcacik -- thank you for your bug report.

This is a known issue in the upstream encfs project (vgough#174), but unfortunately there is no fix available yet. I will keep my eye on this and see if anything changes, though.

[vovcacik]

Also the fact that the encfs config file is leaking to encrypted disk may not be tied to the .encfs6.xml filename or the fact it is config file, but rather to my observation that any file which content starts with <?xml is leaked (that includes the config file also).

[benrubson]

As a workaround you should be able to specify an alternate configuration file (so to move your configuration file somewhere else) thanks to vgough#474.

[vovcacik]

@benrubson yeah that would be handy.

[benrubson]

Finally vgough#478 will ignore configure file .encfs6.xml in reverse mode.

[jetwhiz]

I've pulled in this patch and it looks like that fixes this issue, so this will be available in the next release candidate!