Comment by vishnumohandas
5 years ago
- Mature libsodium clients were available across the platforms we were targeting. The APIs seemed well documented and turned out to be a delight to consume.
- There are access control checks in place to revoke access to files from removed album participants. But from a cryptographic standpoint, once your keys have been shared (/compromised), the respective files should be re-encrypted.
Thanks for answering! Regarding the second point, does the application do this automatically or is the user expected to re-encrypt data manually?
We don't handle this case right now, have added this to our roadmap[1].
I feel that for our use case of storing and sharing personal photos, this might be an over kill. But I'll let the customers decide. There might be usecases I might not have thought of.
[1]: https://roadmap.ente.io/option-to-download-re-encrypt-and-re...
That's exactly the problem I'm facing. Especially if there are multiple shares to the same data it gets tricky. Love to see public roadmaps in products btw.!
1 reply →