4 ms·

I don't think they would be able to do anything about it, since (from what I could infer from reading) it is zero-knowledge, so no one from the company can acce

I don't think they would be able to do anything about it, since (from what I could infer from reading) it is zero-knowledge, so no one from the company can access the pictures. I might be wrong, though

user-the-name 5y ago
Yes, and that is a problem.
- mynameismon 5y ago
  What is the problem/why is there a problem?
  - shuckles 5y ago
    When push comes to shove, technology is subservient to society: https://en.m.wikipedia.org/wiki/Lavabit https://en.m.wikipedia.org/wiki/Lavabit
  - user-the-name 5y ago
    Well, first and foremost, if I ran a service, I would not want to help either terrorists or pedophiles. I would be very unhappy if I was doing that. Secondly, if you do provide service to terrorists or pedophiles, and take no steps to stop doing so, law enforcement and society in general is not going to be very happy with you.
  - deleted 5y ago
    [deleted]
cf_ 5y ago
Well, depending on legislation, they could be ordered to change the code to send the user password to them on next login for that account and then decrypt everything…
- deleted 5y ago
  [deleted]
- commoner 5y ago
  The architecture of Ente (https://ente.io/architecture https://ente.io/architecture) prevents your unencrypted master key from being exposed to the server. The password authentication appears to be client-side, which means that the data could not be compromised solely by a malicious server-side change. Now, Ente could still change its web application to somehow leak the master key and not disclose the changes in the source repo. One solution for this vulnerability is to package the entire web client as a browser extension, which is what Mega is doing: https://github.com/meganz/web-extension https://github.com/meganz/web-extension
  - dane-pgp 5y ago
    There are a couple of other ways to mitigate the problem for web applications. If you're willing to install a browser extension, then it might make more sense to use the Signed Pages extension[0] which applies PGP signature checking to web pages. The other solution is to use Secure Bookmarks[1], which combine SRI integrity hashes with Data URIs to ensure that a fixed bundle of JavaScript is running in the page. [0] https://github.com/tasn/webext-signed-pages https://github.com/tasn/webext-signed-pages [1] https://coins.github.io/secure-bookmark/ https://coins.github.io/secure-bookmark/

user-the-name 5y ago

Yes, and that is a problem.

mynameismon 5y ago
What is the problem/why is there a problem?
- shuckles 5y ago
  When push comes to shove, technology is subservient to society: https://en.m.wikipedia.org/wiki/Lavabit https://en.m.wikipedia.org/wiki/Lavabit
- user-the-name 5y ago
  Well, first and foremost, if I ran a service, I would not want to help either terrorists or pedophiles. I would be very unhappy if I was doing that. Secondly, if you do provide service to terrorists or pedophiles, and take no steps to stop doing so, law enforcement and society in general is not going to be very happy with you.
- deleted 5y ago
  [deleted]

cf_ 5y ago

Well, depending on legislation, they could be ordered to change the code to send the user password to them on next login for that account and then decrypt everything…

deleted 5y ago
[deleted]
commoner 5y ago
The architecture of Ente (https://ente.io/architecture https://ente.io/architecture) prevents your unencrypted master key from being exposed to the server. The password authentication appears to be client-side, which means that the data could not be compromised solely by a malicious server-side change. Now, Ente could still change its web application to somehow leak the master key and not disclose the changes in the source repo. One solution for this vulnerability is to package the entire web client as a browser extension, which is what Mega is doing: https://github.com/meganz/web-extension https://github.com/meganz/web-extension
- dane-pgp 5y ago
  There are a couple of other ways to mitigate the problem for web applications. If you're willing to install a browser extension, then it might make more sense to use the Signed Pages extension[0] which applies PGP signature checking to web pages. The other solution is to use Secure Bookmarks[1], which combine SRI integrity hashes with Data URIs to ensure that a fixed bundle of JavaScript is running in the page. [0] https://github.com/tasn/webext-signed-pages https://github.com/tasn/webext-signed-pages [1] https://coins.github.io/secure-bookmark/ https://coins.github.io/secure-bookmark/