Comment on NoPlainText: One time, browser-encrypted messagingparentComments−brownbat14yMoreover, if the server stores enough information for a recipient to read the message, then the server effectively stores the message.−brownbat14yHmm, oh, I think the stuff after the hash is the decryption key, and we're assuming the server throws it away.We still require a trusted third party here.−StavrosK14yThe HTML anchor never reaches the server in the request, it's for local use only. Of course, malicious JS on the page can always send it anywhere.
Comments
Moreover, if the server stores enough information for a recipient to read the message, then the server effectively stores the message.
Hmm, oh, I think the stuff after the hash is the decryption key, and we're assuming the server throws it away.
We still require a trusted third party here.
The HTML anchor never reaches the server in the request, it's for local use only. Of course, malicious JS on the page can always send it anywhere.