Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

.encfs6.xml treated as file when using no filename encryption #174

Closed
RunasSudo opened this issue May 28, 2016 · 2 comments · Fixed by #478
Closed

.encfs6.xml treated as file when using no filename encryption #174

RunasSudo opened this issue May 28, 2016 · 2 comments · Fixed by #478

Comments

@RunasSudo
Copy link

RunasSudo commented May 28, 2016

When using no (‘Null’) filename encryption, available through expert configuration mode, .encfs6.xml is displayed as a file in the mounted volume, and can even be deleted. Attempting to access the file gives gibberish, or causes an I/O error if MAC verification is enabled.

Vaguely related to #101 in that both relate to encfs being blind to the special nature of .encfs6.xml.

@RunasSudo RunasSudo changed the title .encfs6.xml displayed as file when using no filename encryption .encfs6.xml treated as file when using no filename encryption May 28, 2016
@rfjakob rfjakob added the bug label Jun 1, 2016
@RunasSudo
Copy link
Author

As an addendum: this is particularly problematic when attempting to use encfsctl export which returns a MAC comparison failure and crashes.

@RunasSudo
Copy link
Author

A workaround is to store the .encfs6.xml file outside of the encrypted directory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants