Oblivious Transfer (OT) Protocols
What you'll learn: You'll understand how oblivious transfer lets one party retrieve information without revealing which piece they selected.
The Magic of Selective Privacy
Imagine a database owner has multiple files, and you want to download exactly one—but you don't want the owner to know which file you chose. At the same time, you should only get the one file you requested, not all of them. This seemingly impossible privacy requirement is exactly what Oblivious Transfer (OT) accomplishes.
How OT Works (Conceptually)
In a simple 1-out-of-2 OT protocol:
- The sender has two messages:
m₀andm₁ - The receiver wants to learn one message (say
m₁) without revealing their choice - After the protocol:
- The receiver learns only
m₁(notm₀) - The sender doesn't know whether the receiver chose
m₀orm₁
- The receiver learns only
Think of it like a vending machine with opaque doors: you press a button behind a privacy screen, one compartment opens on your side only, and the machine owner can't see which button you pressed.
Why OT Matters for MPC
Oblivious Transfer is a fundamental building block for secure multi-party computation protocols, especially garbled circuits (which you've already learned). OT enables one party to obliviously retrieve the correct decryption keys for circuit evaluation without revealing their private inputs.
OT protocols typically use public-key cryptography and clever mathematical properties to achieve this two-way privacy guarantee.
Key Takeaway: Oblivious Transfer protocols enable private information retrieval where the receiver learns exactly one chosen item without the sender knowing which item was selected—a crucial primitive for building secure multi-party computation systems.