Please add an explicit warning for cloud services to README.md about securefs HOT 5 CLOSED

I am aware of the problem and plan to add explicit file locking to prevent the users from having multiple securefs instances on the same synchronized directory over different machines. I also plan to change the default format to allow your use case.

from securefs.

You are right about how it is important for multiple machines to run securefs simultaneously. I only use cloud services as backups so I didn't design for such use cases initially.

from securefs.

Thank you for the quick response(s)! I was not criticising the design, but appreciate that you consider the additional use case. Your project is the only one that, in terms of technology, works on all the 3 major platforms. gocryptfs doesn't run well on Windows and macOS, ecryptfs runs on Linux only, and encfs is insecure.

What my ticket was about is that this design choice is not obvious to the user. Especially so since cloud services are mentioned explicitly.

Not knowing about the current limitation may result in loss of data. Please make it visible/obvious until the necessary changes are made.

from securefs.

By the way, you can recover your data with securefs fix, if the losses are not just test data.

from securefs.

The new format has become stable. You can test it now by building from the latest master commit. I will release in a few days.

from securefs.