In summary, I am seeing this issue “out-of-the-box” on a clean macOS Ventura with the latest version of Cryptomator using Google Drive. At present the only rsync workaround is to add “–checksum” to determine file changes based on checksums rather than size/times, but this is 1000x slower.This is obvious to see from the Terminal: compare “ls -l /Volume/source/file” to “ls -l /Volume/Cryptomator/file” and you will see the different timestamps.rsync interprets this timestamp difference as a file change and re-copies every file. Web and mobile versions of Word, Excel, PowerPoint, OneNote, OneDrive, and more Ad-free Outlook and mobile email and calendar with advanced security features Access to Microsoft support experts Premium value included OneDrive Outlook Best value: up to six people Microsoft 365 Family 99.99 Microsoft 365 Family 99.The reason is that Cryptomator changes all the modification times to when the file was copied to the vault. This process worked fine with Boxcryptor but fails with Cryptomator. ![]() Coming from Boxcryptor, my workflow is to create a vault on Google Drive and use one-way “rsync -archive” to keep files on my (Cryptomator) encrypted volume in-sync with my local offline copy … rsync uses file size and modification time to determine what files to sync.Tap + beside your email, then select Create a new vault. I installed latest Cryptomator 1.6.17 (dmg-4104) on macOS Ventura … this was a fresh install of macOS Ventura on a newly-formatted disk, not an upgrade from previous macOS. To create a new vault on Microsoft OneDrive: Go to Settings and select Vaults.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |