search

jetwhiz / encfs4win

Windows port of EncFS
https://encfs.win
Other
400 stars 41 forks source link

Issue mounting on drive #108

Closed alexis- closed 5 years ago

alexis- commented 6 years ago

Environment

Description

encfs.exe fails to mount decrypted filesystem on a drive letter (D:, ..., Z:)

Expected behavior vs. actual behavior

Using any encrypted encFS folder (newly created on windows, already existing from windows or linux):

Steps to reproduce problem

  1. Run encfs.exe C:\Path\To\Encrypted D:

Relevant logs

C:\Program Files (x86)\encfs>encfs -v "C:\Path\To\Encrypted" D: -- -d
2018-03-23 16:02:46,315 VER [main.cpp:619] Forking encfs as child

2018-03-23 16:02:46,330 VER [main.cpp:697] Root directory: C:\Path\To\Encrypted
2018-03-23 16:02:46,330 VER [main.cpp:698] Fuse arguments: (daemon) (fork) (threaded) (keyCheck) encfs.exe D: -f -d -o use_ino -o default_permissions
2018-03-23 16:02:46,393 VER [FileUtils.cpp:296] found new serialization format
2018-03-23 16:02:46,393 VER [FileUtils.cpp:310] subVersion = 20100713
2018-03-23 16:02:46,393 VER [Interface.cpp:110] checking if ssl/aes(3:0:2) implements ssl/aes(3:0)
2018-03-23 16:02:46,393 VER [SSL_Cipher.cpp:328] allocated cipher ssl/aes, keySize 32, ivlength 16
2018-03-23 16:02:46,408 VER [FileUtils.cpp:1613] useStdin: 0
EncFS Password:
2018-03-23 16:02:56,273 VER [Interface.cpp:110] checking if ssl/aes(3:0:2) implements ssl/aes(3:0)
2018-03-23 16:02:56,289 VER [SSL_Cipher.cpp:328] allocated cipher ssl/aes, keySize 32, ivlength 16
2018-03-23 16:03:00,570 VER [FileUtils.cpp:1622] cipher key size = 52
2018-03-23 16:03:00,570 VER [Interface.cpp:110] checking if nameio/block(4:0:2) implements nameio/block(4:0)
jetwhiz commented 6 years ago

Hi @alexis-

encfs4win is already handling dokany daemon mode with its built-in fork, so it is not necessary to do this yourself. Can you try running this without passing the "-d" flag through to dokany and see if this helps? (only encfs -v "C:\Path\To\Encrypted" D:)

alexis- commented 6 years ago

Certainly. I assumed it was used for debugging, as per my understanding of -h "FUSE options: -d -o debug enable debug output (implies -f)"

The behavior appears to be the same.

On the other hand, for some reason after trying again with the drive letter D: (I had changed and tried using A: when all my attempts failed), Windows now reports that EncFS has crashed. I must have missed something before ! I tried to repeat the operation several time: sometimes it will crash and display the D: drive with a question mark "?", and sometimes it will display the Dokan drive, and crash when I try browsing it (double click on D:).

The program output is the same as the initial report. How could I provide you with more material to work ?

alexis- commented 6 years ago

After some more fiddling, here is what comes out:

To provide some context, this is a fresh Windows 10 installation, with last updates. Perhaps I missed these information, in fact I entirely failed to find relevant documentation !

Have a great week-end, and thanks for your work.

jetwhiz commented 5 years ago

@alexis- does this error only occur with drive letter D? I can't seem to replicate this issue on my end except when a drive letter is already used on the system. Also, can you try with the latest version of encfs4win (RC14)? It ships with the latest Dokany (v1.2).

stale[bot] commented 5 years ago

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.