← Back to context

Comment by Retr0id

17 hours ago

That's not mitigating client compromise, that's a whole other thing - trying to construct an uncompromiseable client.

You don't build defense-in-depth by assuming something can't be compromised.

Clients can always be compromised. I'm not talking about a client that can't be compromised, but simply a client that is not compromised out-of-the-box.

  • That seems orthogonal to the subject of this discussion, i.e. "Compromise of the client side application or OS shouldn't break the security model."