#104 Dropbox conflicted copies provoke recurring syncs

[Anonymous]

Originally created by: mfsteixe...@gmail.com

What steps will reproduce the problem?
1. create file with same name on two computers
2. let them sync to dropbox
3. dropbox will create conflict (an easy way to make this happen is disable the network on the first machine, create the file on the second and then re-enable the network, this way the second file gets created before dropsbox has time to sync it)

when this happens, sometimes lots of conflicts occur in dropbox.
Here's what I think happens: cryptsync decrypts both the file and the conflict to the same file (because it uses the filename inside 7z), if the conflicted copy is decrypted after the "correct" file cryptsync will encrypt it again to dropbox folder

It is unpredictable which file gets to be the one on the unencrypted folder on both computers...

This can be avoided if cryptsync names the decrypted file after the file name of the encrypted one and not the filename stored in the 7z file.

That way there would be a file named "[...]conflicted copy[...]" in the unencrypted folder and I could check it out.

My Request is then for an Option like "Preserve filename on decrypted file" or "don't use filenames stored in 7z"
(of course this option is only available if filenames are not encrypted)

Thank You

[Anonymous]

Originally posted by: n...@bitnology.com

I also have recurring syncs but happening with encrypted filenames.

In the case of encrypted filenames, cryptsync should be able to look at the filename and realize when it is a conflicted copy because the filename is the encrypted filename plus e.g. "Wally's conflicted copy".

In this case the extra text could be simply appended to the decrypted filename?

Maybe the option could be called "Preserve conflicted copy"? It would be great if Cryptsync could one-up Dropbox by warning of a conflicted file!

Would it be justifiably to classify this one as "High" since when this happens it can very quickly fill up several users' Dropbox space and thus become a significant problem until someone more experienced figures out what's happening. In my case this was happening several folders deep in a tree of many files, really hard to detect if you are not especially looking for it!

Thanks!