Search the Community
Showing results for tags 'true crypt'.
Found 1 result
From what I read the last couple of days around the forum Sync uses AES 128 encryption for the transfers which should be more than enough for most users. But since it's closed source and most security concerned people prefer to have the control in their own hands I believe a lot of people will be syncing AES 256 TrueCrypt containers. Here is what I have learned so far, please correct/add things so we can make one stop, best practices thread for syncing encrypted stuff. - Sync works well with fixed size encrypted containers. It splits the files in 4mb chunks and will only re-transfer the chunks that have been changed. - If the container is not fixed size and even one byte is added or removed it will re-ransfer the whole container because it can't track shifted data. - On some OS you will have to set TrueCrypt to update the last modified date, so Sync can understand the file is modified and sync it. (By default TryeCrypt doesn't change the container date) On other OS that is not needed (some clarification from people in the known why the behavior is different will be appreciated) - No matter how much data you've changed in your container you will have to dismount it, in order for Sync to be able to sync, since it doesn't sync files in use. (Right?) Please note, this is information I found around the forum, i'm just about to start testing that myself. So, if there are people with actual experience, it will be really useful if they can confirm that and add their own observations and advises. I'm also very interested if someone managed to corrupt a container already by syncing it? In that case does the trash folder helps? Generally lets make this a thread that would be enough for everyone to read and start syncing encrypted stuff safely right away in an optimal way.