Open cesarpachon opened 3 years ago
Hi all, I'm facing the same error message, but for more than half my files. And, stupidly as now I realize, never thought to create backups of the encrypted volume itself, just on the inside. So, same question as cesarpachon - and also, is there something we can do to help you help us?
Did you follow this when creating it? https://github.com/vgough/encfs/blob/c444f9b9176beea1ad41a7b2e29ca26e709b57f7/README.md#what-settings-should-i-use-for-dropbox
Personally, I commit mine git however this has risks such as weakening cryptography with multiple copies of the same file.
Ah, I hadn't known about those instructions back then (perhaps hadn't looked at it because it's not Dropbox for me but Nextcloud, can't remember). Didn't see or choose something called "paranoia mode", either, though. In hindsight, git would have been a really good idea, weakened cryptography or not...
There's also git-crypt which uses GPG. I haven't used it, yet but looks promising.
If you want I can create a proof of concept which is private file store oriented.
hi, I noticed multiple corrupted files ("Bad Message" when trying to access them). I have my encrypted folder in Dropbox, so I read the issues here and I found related issues: https://github.com/vgough/encfs/issues/388 https://github.com/vgough/encfs/pull/390 I would like to confirm if there is nothing to do to recover those damaged files, and if there similar known issues with other services like Mega, or recommendations on how to properly setup a s3 bucket for personal usage? thanks