Public Key Infrastructure ยท 4.1

๐Ÿค” The Trust Problem

A public key is useless if you can't verify who it belongs toโฑ ~2 min

๐Ÿ“žHow do you know you're not talking to an impersonator?

You call your bank. Someone picks up and sounds professional. They ask for your account number. But how do you know this is actually your bank and not an impersonator who rerouted your call? In cryptography, this is the man-in-the-middle problem. Alice wants Bob's public key โ€” but how does she know the key she receives is really Bob's and not an attacker's?

The Man-in-the-Middle Attack

  1. 1.Alice asks for Bob's public key
  2. 2.Mallory (attacker) intercepts the request and substitutes her own public key
  3. 3.Alice encrypts to Mallory's key, thinking it's Bob's
  4. 4.Mallory decrypts, reads or modifies the message, re-encrypts with Bob's real key, forwards to Bob
  5. 5.Alice and Bob think they're talking to each other; Mallory reads everything
โš  WarningThis attack is why you can't just exchange public keys over an untrusted channel and trust them blindly. You need a way to verify that a public key genuinely belongs to a specific entity. This is exactly the problem that Public Key Infrastructure (PKI) solves.

The PKI Solution: Trusted Third Parties

PKI solves the key verification problem by introducing Certificate Authorities (CAs) โ€” organizations whose public keys come pre-installed and trusted in every operating system and browser. A CA digitally signs a certificate that binds a public key to an identity (a domain name, an organization, a person). Because you trust the CA, and the CA vouches for the binding, you can trust the certificate.

โ˜… FactYour browser and OS come with approximately 150 pre-trusted root CA certificates. When you visit google.com, your browser checks: is this certificate signed by one of those 150 trusted roots (or a CA they trust)? If yes, the connection is trusted.
๐Ÿง Quick Checkfirst try = +5 XP

PKI exists to solve which problem?

โญ 0 XP๐Ÿ”ฅ 0 days