3 ms·
I wonder how Cryptomator [0], EncFS [1] or gocryptfs [2] stacks up. [0] https://cryptomator.org/ https://cryptomator.org/ [1] https://vgough.github.io/encfs/
by jszymborski 2y ago
I wonder how Cryptomator [0], EncFS [1] or gocryptfs [2] stacks up.
[0] https://cryptomator.org/ https://cryptomator.org/
[1] https://vgough.github.io/encfs/ https://vgough.github.io/encfs/
[2] https://github.com/rfjakob/gocryptfs https://github.com/rfjakob/gocryptfs
- tptacek 2y agoIf they aren't multitenant systems it doesn't make sense to compare them to the targets of this paper.
- jszymborski 2y agoI suppose I meant for the specific use case where you store and sync the encrypted file systems with cloud providers like e.g. Dropbox or pCloud. But perhaps I've misunderstood you.
- traceroute66 2y ago> I suppose I meant for the specific use case where You're missing the point. Anybody can download $insert_name_of_your_favourite_software and use that to encrypt data before uploading to cloud storage. The point here is the discussion about multi-tenant cloud-based solutions. You know, the sort of thing you use in a work environment when you share documents with your colleagues. In that context, the DIY $my_favourite_tool pre-encrypt route is simply not feasable or scalable and would be hell on earth to manage and maintain.
- jszymborski 2y agoI understand now, thanks :)