Larry Heller

I am a developer (retired) and have given this problem some thought. In case anyone is interested in writing some code, here is a possible solution. This addresses the use case where there is ONE encrypted repository and one or more unencrypted synced copies, which would seem to be the primary use case for "multiple computers": What we need to do is maintain a "system" file in the encrypted area, or rather, one such file in each directory which has had children (files or subdirectories) deleted -...

I am using CryptSync 1.2.7.338 on Windows 10. I too have the same problem. Two or more computers doesn't seem to work when files are deleted or renamed - the file disappears in the encrypted path and then cryptsync readds it from the second computer's unencrypted path. (Iactually tested this with two folders on one computer) It seems like deletion is really not two way sync - it only is triggered by deleted the unencrypted file (on the first computer in this case); if you delete the encrypted file...

I am using CryptSync 1.2.7.338 on Windows 10. I too have the same problem. Two or more computers doesn't seem to work when files are deleted or renamed - the file disappears in the encrypted path and then cryptsync readds it from the second computer's unencrypted path. (Iactually tested this with two folders on one computer) It seems like deletion is really not two way sync - it only is triggered by deleted the unencrypted file (on the first computer in this case); if you delete the encrypted file...

I am using CryptSync 1.2.7.338 on Windows 10. I too have the same problem. Two or more computers doesn't seem to work when files are deleted or renamed - the file disappears in the encrypted path and then cryptsync readds it from the second computer's unencrypted path. (Iactually tested this with two folders on one computer) It seems like deletion is really not two way sync - it only is triggered by deleted the unencrypted file (on the first computer in this case); if you delete the encrypted file...