[mschuster91]

This can protect against malicious browser extensions recording POST/GET-transmitted data (toolbars!!!), as the content will be encrypted at that stage.

Furthermore, this helps against content disclosure if the server is compromised.

[fooyc]

If your browser is untrusted, you are doomed.

> Furthermore, this helps against content disclosure if the server is compromised.

If the server is compromised, openpgp.js is compromised too.

[willvarfar]

Presuming the private key for the messages is not on the server, then old messages will not be compromised.

A kind of perfect secrecy for messages.

[fooyc]

No need to do this on the client side then (that was my point)

[willvarfar]

You could do the exact same thing on the server, but that's using server's CPU instead of clients?

[manojlds]

Forward secrecy with https? https://community.qualys.com/blogs/securitylabs/2013/08/05/c...

[willvarfar]

yeah its often called perfect forward secrecy - PFS - too.

http://en.wikipedia.org/wiki/Perfect_forward_secrecy