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

Can't mount existing encfs filesystems #1

Closed
noamfreedman opened this Issue Apr 16, 2014 · 4 comments

Comments

Projects
None yet
3 participants
@noamfreedman
Copy link

noamfreedman commented Apr 16, 2014

I have a pair of existing encfs filesystems that I can't mount. I let it auto-report, but let me know if you need anything else. The error was:

"Unknown error occurred while mounting existing Safe. Please help us improve by sending a bug report. It's automatic and no personal information is used."

@rianhunter

This comment has been minimized.

Copy link
Contributor

rianhunter commented Apr 18, 2014

I'm super sorry to hear that. I can verify that your bug report came through: http://dyn.www.getsafe.org/dyn/exceptions/35 (I think this might be you)

Can you do me a favor? Can you paste the contents of running the following commands on your EncFS volumes (where they work)?

$ encfsctl --version
$ encfsctl info <root_dir>

Then I'll create volumes with the same configuration and try to figure out what's wrong with Safe's EncFS fork.

@Whoops

This comment has been minimized.

Copy link

Whoops commented Apr 22, 2014

Same for me on OS X Mavericks.
encfsctl version 1.7.4
Version 6 configuration; created by EncFS 1.7.4 (revision 20100713)
Filesystem cipher: "ssl/aes", version 3:0:0 (using 3:0:2)
Filename encoding: "nameio/block", version 3:0:0 (using 3:0:1)
Key Size: 192 bits
Using PBKDF2, with 134156 iterations
Salt Size: 160 bits
Block Size: 1024 bytes
Each file contains 8 byte header with unique IV data.
Filenames encoded using IV chaining mode.
File holes passed through to ciphertext.

@noamfreedman

This comment has been minimized.

Copy link

noamfreedman commented Apr 22, 2014

Sorry for the delay... For me:

encfsctl version 1.7.4

Version 5 configuration; created by EncFS 1.3.2 (revision 20040813)
Filesystem cipher: "ssl/aes", version 2:1:1 (using 3:0:2)
Filename encoding: "nameio/block", version 3:0:1
Key Size: 256 bits
Block Size: 512 bytes
Each file contains 8 byte header with unique IV data.
Filenames encoded using IV chaining mode.

@rianhunter

This comment has been minimized.

Copy link
Contributor

rianhunter commented Apr 22, 2014

Thanks will dig in and hopefully next release will have the fix.

@rianhunter rianhunter closed this in b3436dd May 4, 2014

rianhunter added a commit that referenced this issue May 4, 2014

tinyxmlparser: revert c7a9aea265b8, Fixes #1
c7a9aea265b8 was an early attempt to work around a GCC bug preventing
Safe from building with -flto. Unfortunately it was also an incorrect
workaround. This reverts that change and fixes GitHub issue #1
"Can't mount existing encfs filesystems."

--HG--
extra : amend_source : 490535441b1161c8fc23f2929462cbd492b12f8d
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment