desktop.ini related problems

[jetwhiz]

In reverse mode, Windows attempts to create desktop.ini files in the encrypted folder (which encfs thinks is an encrypted filename), resulting in "checksum mismatch" errors.

###Create 0084
CreateFile: \io0j\desktop.ini
        DesiredAccess: FILE_GENERIC_READ
        ShareAccess: FILE_SHARE_DELETE|FILE_SHARE_WRITE|FILE_SHARE_READ
        Disposition: FILE_OPEN (1)
        Attributes: 0 (0x0)
        Options: 100 (0x64)
2016-11-28 22:07:57,413 VER [StreamNameIO.cpp:177] checksum mismatch: expected 43402, got 52295
###Create 0085
CreateFile: \
        DesiredAccess: SYNCHRONIZE
        ShareAccess: 0x0
        Disposition: FILE_OPEN (1)
        Attributes: 0 (0x0)
        Options: 33 (0x21)
2016-11-28 22:07:57,444 VER [StreamNameIO.cpp:178] on decode of 6 bytes
2016-11-28 22:07:57,475 ERROR [default] withFileNode: error caught in getattr: checksum mismatch in filename decode
CreateFile status = 0
CreateFile status = c0000034
###QueryVolumeInfo 0085
GetVolumeInformation
###Create 0086
CreateFile: \
        DesiredAccess: SYNCHRONIZE
        ShareAccess: 0x0
        Disposition: FILE_OPEN (1)
        Attributes: 0 (0x0)
        Options: 33 (0x21)
###Cleanup 0085
Cleanup: \

CreateFile status = 0
###Close 0085
Close: \

desktop.ini files also cause problems when attempting to rename/move/delete folders. maybe we should refuse to allow Windows to create desktop.ini files?

[vovcacik]

You've got such a nice and detailed log. I run encfs with -f -v but I dont have the level of detail you have.

[jetwhiz]

Hi @vovcacik -- this is with Dokany debug output enabled. You can do this with:

encfs.exe path mountpoint -- -d

[stale[bot]]

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.