Course contentsShow
← Security
Lesson 2945 of 3,05255. Secure CommunicationsFree lesson

Identity Verification in E2EE

Safety numbers, key fingerprints, and out-of-band verification methods to prevent man-in-the-middle attacks.

Identity Verification in E2EE

You'll learn how end-to-end encrypted systems confirm you're truly talking to the right person, not an impostor.

The Core Problem

In E2EE systems like Signal, your messages are encrypted with your contact's public key. But here's the catch: how do you know that key actually belongs to your friend and not an attacker who inserted themselves in the middle? Without identity verification, a man-in-the-middle (MITM) attack could compromise even perfect encryption.

Safety Numbers and Key Fingerprints

E2EE apps generate safety numbers (also called key fingerprints)—unique identifiers derived from the combination of both users' public keys. Think of them like a shared secret password that only legitimate participants can compute correctly.

In Signal, for example, each conversation has a 60-digit safety number. If an attacker swapped keys during the initial handshake, their fraudulent safety number would differ from the legitimate one.

Out-of-Band Verification

The gold standard is out-of-band verification—comparing safety numbers through a completely separate channel:

  • In person: Meet face-to-face and scan each other's QR codes (which encode the safety number)
  • Phone call: Read the numbers aloud to each other
  • Video call: Show the numbers on screen
  • Trusted intermediary: A mutual friend confirms both parties' fingerprints

This separation ensures an attacker controlling your messaging channel cannot also manipulate the verification process.

Why It Matters

Without verification, you're trusting the server to deliver correct keys. Out-of-band verification removes that trust requirement, turning E2EE from "probably secure" into "cryptographically proven secure against MITM."

Key Takeaway: Identity verification through safety numbers and out-of-band confirmation is the critical final step that transforms E2EE's mathematical guarantees into real-world protection against man-in-the-middle attacks.