Closed vovcacik closed 5 years ago
Hi @vovcacik -- thank you for your bug report.
This is a known issue in the upstream encfs project (https://github.com/vgough/encfs/issues/174), but unfortunately there is no fix available yet. I will keep my eye on this and see if anything changes, though.
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).
As a workaround you should be able to specify an alternate configuration file (so to move your configuration file somewhere else) thanks to https://github.com/vgough/encfs/pull/474.
@benrubson yeah that would be handy.
Finally https://github.com/vgough/encfs/pull/478 will ignore configure file .encfs6.xml
in reverse mode.
I've pulled in this patch and it looks like that fixes this issue, so this will be available in the next release candidate!
Environment
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
Null
filename encryption method.Relevant logs
Nothing interesting in verbose log.