3 ms·
> I don't see why they would be significantly different from the problems associated with serving a web banking site, and there are plenty of those. With web
by zokier 13y ago
> I don't see why they would be significantly different from the problems associated with serving a web banking site, and there are plenty of those.
With web banking usually the bank has legitimately access to all information they are presenting to you via web. In email your email-provider shouldn't have access to your unencrypted mail.
- Retric 13y agoPresumably you could use client site JavaScript to decode your message. However, that brings up key management issues.
- zokier 13y agoI don't believe that would be good enough. Encryption/decryption should be done by the browser in a way that JS has no access to either the keys or the cleartext. There should be also clear indications in the browser chrome when accessing such elements.
- kybernetikos 13y agoI suppose the key point is that you can't trust whomever is storing your data with storing your email app code - it's far too easy for them to serve you backdoored app code if they're required to by the government.