Need to see if your shared folder is taking up space on your dropbox 👨💻? Find out how to check here.
Forum Discussion
Solved
Block-level sync for VeraCrypt not working post 83.4.152 update
Greetings all,
After DB auto-updated to 83.4.152, I noticed that the block-level syncing doesn't seem to be detecting changes anymore for my VeraCrypt container.
Before the update, everytime I di...
Hi all, we've brought this to our team and wanted to follow up.
While we've presented a workaround: either by turning off the "preserve file modification timestamps" setting in the application or naming the file with a ".tc" or ".hc" extension, we want to be transparent about our current priorities and unfortunately, this means that we won't be able to delve deeply into this in the near future.
We're still tracking these reports, and will make sure to inform you right away of any changes.
Thanks for understanding .
Julia20
Dropbox Staff
Dropbox StaffHi everyone.
Follow-up on my post above. We allow using ".tc" and ".hc" extensions as a work around. In the meanwhile we are looking into a better long term solution.
Thank you for your patience!
Julia
Julia any reason why this no longer works?
as Dropbox has a workaround, dropbox should now know what caused this
have you already tried to beta-version that is mentioned here?
Reason why it is not sufficient to have block-level-sync for *.tc and *.hc. files only:
VeraCrypt is a security tool, where you can work with containers. So with having to rename the files to a specific extension (tc, hc), this lowers security because the file extension already indicates, which type of container a file is.
no, I have not.
I stopped installing any Dropbox beta builds about 2 years ago, when they stopped doing change logs. Also here, there is no change log or mentioning of this fix in the beta build thread referred, I cannot verify if the link points to a correct or other build.
There are now 3 newer beta builds, do they all contain this fix or not? again, no relevant change logs. or is it already in the newest stable build, just relased 2 days ago? limit change log, but no mentioning of this fix.
Based on this limiteded/incomplete/missing information, I will not waste my time testing this.
Besides I now finally had enough of this type of dropbox behaviour,
I already moved my containeres to my own seafile based cloud solution.
