4 ms·

VeraCrypt is good but it doesn't work well with syncing, because changing any bit of the disk image invalidate the whole disk hash. Cryptomator works a bit diff

VeraCrypt is good but it doesn't work well with syncing, because changing any bit of the disk image invalidate the whole disk hash. Cryptomator works a bit differently (it changes the structure/names, but store the underlying encrypted files as files) so you can sync file by file.

ale42 3y ago
I think that VeraCrypt and Cryptomator have very different use cases. And VeraCrypt has features like hidden volumes (not that most people would ever need those).
aborsy 3y ago
Veracrypt is a disk encryption tool, not for syncing!
- maattdd 3y ago
  I don't think you've understood my comment.
  - aborsy 3y ago
    I have done this and been there before. Dropbox syncs the deltas in LUKS and veracrypt disks. A change of a bit in plaintext changes the blocks that are involved, and only those blocks are updated. But most other sync tools don’t handle it properly. That was around a decade ago. Today, one would use cryptomator, rclone, gocryptfs rtc.
MikusR 3y ago
And propper syncing tools can sync only the changed parts.
- maattdd 3y ago
  Do you know a syncing tool which would work with a VeraCrypt image? (rsync algo doesn't for example)
  - Groxx 3y ago
    Rsync syncs only differing blocks of data (not whole files) by default - it's pretty much the reason it is so popular. There are a lot of ways to lose that though. No rsync able to run and calculate block checksums on the other machine -> no block syncing. Change a byte in a file in an encrypted volume -> it might copy-on-write and make a wholly new encrypted "file" with everything different in the final encrypted data. Etc, it depends on a bunch of stuff interacting in ways that they might have legitimate reasons to not support, particularly with security/privacy sensitive stuff. Not sure what you're encountering, but if it's important to you there are a few ways to troubleshoot it. It might be possible to get it working.
    - zeroimpl 3y ago
      By default if rsync sees any difference in metadata (timestamps), it just copies over the file fresh - first to a temporary file and then renames over the original. To do an in-place update you'd need to specify an arg for that. And even then, it needs to do a full read of both files to compare, so all it saves on is bandwidth.
  - brokenmachine 3y ago
    Syncthing uses block syncing, so I imagine it would work well, although I haven't tried.
  - aeyes 3y ago
    Works fine with rsync here.
apankrat 3y ago
This can be remedied by using tools that can do block-wise (delta) copying of large files, e.g. https://bvckup2.com/kb/delta-copying https://bvckup2.com/kb/delta-copying

ale42 3y ago

I think that VeraCrypt and Cryptomator have very different use cases. And VeraCrypt has features like hidden volumes (not that most people would ever need those).

aborsy 3y ago

Veracrypt is a disk encryption tool, not for syncing!

maattdd 3y ago
I don't think you've understood my comment.
- aborsy 3y ago
  I have done this and been there before. Dropbox syncs the deltas in LUKS and veracrypt disks. A change of a bit in plaintext changes the blocks that are involved, and only those blocks are updated. But most other sync tools don’t handle it properly. That was around a decade ago. Today, one would use cryptomator, rclone, gocryptfs rtc.

MikusR 3y ago

And propper syncing tools can sync only the changed parts.

maattdd 3y ago
Do you know a syncing tool which would work with a VeraCrypt image? (rsync algo doesn't for example)
- Groxx 3y ago
  Rsync syncs only differing blocks of data (not whole files) by default - it's pretty much the reason it is so popular. There are a lot of ways to lose that though. No rsync able to run and calculate block checksums on the other machine -> no block syncing. Change a byte in a file in an encrypted volume -> it might copy-on-write and make a wholly new encrypted "file" with everything different in the final encrypted data. Etc, it depends on a bunch of stuff interacting in ways that they might have legitimate reasons to not support, particularly with security/privacy sensitive stuff. Not sure what you're encountering, but if it's important to you there are a few ways to troubleshoot it. It might be possible to get it working.
  - zeroimpl 3y ago
    By default if rsync sees any difference in metadata (timestamps), it just copies over the file fresh - first to a temporary file and then renames over the original. To do an in-place update you'd need to specify an arg for that. And even then, it needs to do a full read of both files to compare, so all it saves on is bandwidth.
- brokenmachine 3y ago
  Syncthing uses block syncing, so I imagine it would work well, although I haven't tried.
- aeyes 3y ago
  Works fine with rsync here.

apankrat 3y ago

This can be remedied by using tools that can do block-wise (delta) copying of large files, e.g. https://bvckup2.com/kb/delta-copying https://bvckup2.com/kb/delta-copying