busy eating waffles brb

  • 0 Posts
  • 9 Comments
Joined 1 year ago
cake
Cake day: July 19th, 2023

help-circle

  • The server might always send a modified script that just uploads the plaintext private key.

    Yeah, you’d need a way to validate the client code before it’s executed to solve that issue

    Section “2. Client application security” of MEGA’s Security Whitepaper discusses this exact problem. Their best solution to that issue is to just cram the whole frontend in a signed web extension and not serve any code to the user when the extension is active, which is not very user friendly but works for those who want an extra layer of protection

    I just can’t find a good user-friendly implementation, sorry for not being of more help. The web just isn’t E2EE-friendly ig :/


  • Yeah, I’m not used to E2EE in the browser either and StackExchange seems to agree that there’s no nice solution :/

    The sanest option in terms of user practicality to me appears to be storing the private key on the server, maybe encrypted with the user’s password, and sending it to the user on successful login where it would be decrypted client side. It seems like it’s more or less what MEGA is doing since they have a similar issue

    If the server having temporary access to the user’s password is an issue maybe the password could be partially pre-hashed before being sent?

    It’s be interesting to talk about it with someone with more experience, especially since implementing all of that will be a pain so it can’t be redone every Thursday







  • No. If you want to run an algorithm you should run it on your computer and not on somebody else’s.

    Ignoring the fact that having a proper recommendation AI for every single user would be environmentally disastrous, it would also place much more burden on the ones hosting instances. Keep in mind that most instances are hosted by people who do not earn anything from them and that many bigger instances already had to rent bigger servers because of the influx of people. Adding computationally expansive algorithms in the mix would just increase the cost for the volunteers on top of signing the death of some smaller instances run on a tight budget.

    It would also be prone to recreating the SEO mess that we can see today on social medias like youtube where, if you want to grow your community, satisfying the algorithm becomes more important than the actual content of your posts.

    However, I would have no issues with an algorithm that a user of an instance could run on their devices and tweak to their liking. This solution would probably be less convenient but would avoid most of the mess.

    EDIT: Sorry if my comment came out as too aggressive and thank you for making this post. I think that’s an important issue to discuss and, as thanks for bringing it up, you have my upvote :)