Drive now corrupt after turning on filename encryption - no help from Boris!

cg101

I created a drive with my Mac and paid for the upgrade to unlimited personal as I wanted to take advantage of the filename encryption feature.

I emailed support and Boris responded to say that the only way to turn on filename encryption was to use a Windows PC and download the v1.4 beta to turn it on post creation of the drive.

I therefore did this and in the process and encountered a whole bunch of errors as follows:
"Could not rename the folder..." - Access denied
-and-
"Could not rename the folder..." - Value of '1001 is not valid for 'Value'. 'Value' should be between 'minimum' and 'maximum'. Parameter name: Value

After clicking Cancel a lot of times to get through the errors I tried to access the drive and found all the filenames to be randomized - within Boxcryptor! It is as if it has renamed the files but does not realize the filenames are now encrypted. So I am unable to determine what the files are.

Now I can't decipher my files at all. I have emailed support (Boris) a number of times and no one responds. This is unacceptable - please resolve this or refund me, thank you!

Joe0815

cg,
try accessing your drive from your mac (old version, no filename encryption).
Just my guess, but when BC reads "MyFile.txt" and thinks /this/ is the encrypted filename it decrypts it for you to "wbo78U5t6bNI61".

If that doesn't help try replacing the file ".encfs6.xml" in the root folder by a backup copy and retry accessing.

HTH, Joe

Boris

Hello cg101

I'm sorry but we received no further emails from you in our ticket system.

So if your files are corrupt and you created a backup just replace your corrupted files with the backup. If you have not made a backup you can use the history feature of your cloud storage provider. With this feature you can restore older revision of your files.

Now to successfully enable filename encryption make sure you have full access (read/write) to the BoxCryptor folder on your Windows computer. After that try again and report us if you had again errors.

Best regards
Boris

Robert

An additional comment from my side:

When you enable (or disable) filename encryption, BoxCryptor tries to rename all folders and files within your BoxCryptor Folder which requires full access to those files and folders. BoxCryptor should have detected that access rights are missing in a testing phase which is executed before the actual renaming and aborted.

My questions:
1) Have some files/folders been renamed or do all files in the BoxCryptor Folder still have plaintext filenames?
2) Can you post the contents of the .encfs6.xml configuration file which is in the root of your BoxCryptor Folder (e.g. Dropbox\BoxCryptor.bc\.encfs6.xml)

Best,
Robert

cg101

Thanks for the responses - it is concerning my emails were going into a black hole!

Not all the files have been renamed. When I did the conversion I performed it on a PC I hadn't used for a while so it was sync up with Dropbox when it was converting to secure filenames. I presume this is why this happened? Although some of the errors don't seem to relate to this.

I ended up restoring the files from a back up and starting again this time enabling filename encryption from the start.

For reference the contents of the .encfs6.xml is:

<boost_serialization signature="serialization::archive" version="9"> <cfg class_id="0" tracking_level="0" version="20"> <version>20100713</version> <creator>EncFS 1.7.4</creator> <cipherAlg class_id="1" tracking_level="0" version="0"> <name>ssl/aes</name> <major>3</major> <minor>0</minor> </cipherAlg> <nameAlg> <name>nameio/null</name> <major>1</major> <minor>0</minor> </nameAlg> <keySize>256</keySize> <blockSize>4096</blockSize> <uniqueIV>0</uniqueIV> <chainedNameIV>0</chainedNameIV> <externalIVChaining>0</externalIVChaining> <blockMACBytes>0</blockMACBytes> <blockMACRandBytes>0</blockMACRandBytes> <allowHoles>1</allowHoles> <encodedKeySize>52</encodedKeySize> <encodedKeyData> yG3Re97HTZg8Wm6+FsoyAhUGvi2IGIesWvwW+mBpqcahHUty/O6SnkNuS+H5ilSuSttD9k== </encodedKeyData> <saltLen>20</saltLen> <saltData>914xMwvY3vzolBpEiikRc9qdWLt=</saltData> <kdfIterations>58721</kdfIterations> <desiredKDFDuration>500</desiredKDFDuration> </cfg> </boost_serialization>