Concepts / Cryptography at work

Cryptography at work

HTTPS interception

Also called mitmproxy, rogue CA, rogue certificate, public key pinning

Reading an HTTPS session from a box in the path by forging the server's certificate — which works only once the victim trusts the box's CA, and which certificate pinning defeats even then.

Two TLS sessions, one forged certificate
Two TLS sessions, one forged certificate

The proxy cannot read TLS by watching; it must pose as the server with a certificate signed by its own CA. That works only if the client's trust store holds that CA.

HTTPS interception reads a [[tls|TLS]] session from a proxy in the path, (mitmproxy). The proxy ends the client's TLS itself with a certificate it forges for the real name, and opens a second connection to the server. Its CA is unknown, so the client refuses, unless that CA is added to the [[trust-store|trust store]]; then every site opens. Pinning still refuses: the client expects the server's exact key. See [[man-in-the-middle]].

See it on real machines

Read next

Learn it on real machines.

Every lab is a small network of real Linux machines in your browser. Sign in with Google or email to start.

Start this lab