2 ms·
Where did you get the idea that this can "pass all blocks" ? You can't _pass_ blocks, a Man in the Middle isn't obliged to pass anything from you to the other p
by tialaramex 7y ago
Where did you get the idea that this can "pass all blocks" ? You can't _pass_ blocks, a Man in the Middle isn't obliged to pass anything from you to the other party. You can only decide you'd rather the connection fails than have it be intercepted.
It turns out that humans are strongly disinclined to accept failure. Once they have set upon a course of action they'll see it through despite almost any cost, they are focused on achieving their goal. This is related to the sunk cost fallacy. For interception MITM attacks this means the attack will very likely work _unless_ we just treat it as a failed connection.
If you interrupt a human trying to do something with "The government of Kazakhstan wants to intercept your connection and arbitrarily change everything. OK?" the human doesn't even read as far as "Kazakhstan" before they push OK. "OK already computer, stop bothering me". So there's no point offering failure as an option, users will pick "OK" anyway.
Instead the correct solution is for the browser to just treat interception as failure as a matter of policy. Users aren't surprised if you do this, now the browser just can't connect when there's a problem, which is already how they understood things. And because they can't just press "OK" they are freed from their plan, it has failed, and now they can re-evaluate.