new 1.4: what happen if..?

hpvd

just installed the new 1.4.0.1 - it seems to work fine :-)

there are some short questions regarding to long filepathes:

before (1.3.2) I have some files with to long pathes (after encryption):
they where encrypted but not synced (uploaded)

what happens (sync?) after the update to these files:
1) if i enable long file pathes in the setup?
2) if i diasable filenameencryption (RMB)
a) having enabled 1)
b) having not enabled 1)
3) and what will happen if i activate filename encryption later again?

Thanks very much!

Robert

Hi hpvd,

1) If you enable long paths, you can still access and work with these files in the BoxCryptor Drive as you did before with 1.3.2. If you long path support is disabled (by default), you won't be able to access these files in the BoxCryptor Drive (BoxCryptor will return a "Path too long" error). But you can always enable long path support, rename or move the files and then have access to them again with long path support disabled.

2 and 3) Enabling or disabling filename encryption does always use long paths if necessary so it could produce files which are only accessible with long path support enabled.

Best,
Robert

hpvd

thanks very much for the fast answer!

hpvd

if i have filenames which are to long if the names are encrypted,
and than I disable filename encryption, which result in short enough names
=> will these files be uploaded?
=> and what happens if I enable filename encryption again?

Geronimo

Didn't test it, are both long and short filenames in compliance with EncFS ?

Thanks

Robert

Hi hpvd,

I'm sorry, I have to revise my previous answer - I just double checked our source code and I was wrong on 2) and 3). The correct answer must be:

2) and 3) Enabling or disabling filename encryption follows the long path restriction for the new filenames. If support for long paths is enabled on the drive, it could produce files which are only accessible with long path support enabled (obvious). If support for long paths is disabled (default), the "warm-up tests" for the operation will fail if it would produce any file with a too long path and the operation will be canceled before it started.

Regarding the other questions:

4) If the plaintext filename are then short enough, the files should be synced by the cloud storage provider. If you then enable it again, I would expect the cloud storage provider to remove the file with plaintext filename from its records and _not_ sync the file with encrypted filename. We're performing a simple Rename operation (which might also look like a Move operation to the cloud storage provider). But this is something out of our control and I cannot make a general statement.

5) Support for long paths has nothing to do with EncFS itself. As long as the underlying file system supports long file paths (which almost all modern file systems do), EncFS is able to handle those files (e.g. on Mac OS X).

--Robert