5 ms·

You need to trust the server at some point. Assuming you do then it doesn't matter if the at-rest encryption is done in the browser or on the server. I'd be ha

You need to trust the server at some point. Assuming you do then it doesn't matter if the at-rest encryption is done in the browser or on the server. I'd be happy with HTTPS upload and PGP encryption before writing to disk or forwarding. I think the biggest risk of a secure upload server is a vulnerability exposing a disk full of secure content in the future.

EGreg 10y ago
Your don't need to trust the server. You can implement subresource integrity checks!
- nsgi 10y ago
  Subresource integrity still requires you to trust the server sending the hashes.
  - EGreg 10y ago
    Ok so publish the hashes on a blockchain and have the client verify them there
    - rudolf0 10y ago
      Not a bad idea, but this isn't a thing browsers currently do, and the average person can't do that with ease. Especially considering this web app is aimed at non-tech savvy individuals.
      - roblabla 10y ago
        Make the whole page hosted on IPFS, and make your DNS point to it. Then you just need to trust the DNS. So use namecoin.