Key Discovery and Distribution
What you'll learn: How users find and verify each other's public keys using keyservers, Web Key Directory, DANE, and modern discovery mechanisms.
The Discovery Problem
Having a public key is useless if your correspondent can't find it. Unlike messaging apps where key exchange happens automatically during account setup, email encryption requires users to somehow locate recipient keys before sending encrypted mail. This is the key discovery problem: how do you reliably find Bob's public key when you want to email him?
Traditional Public Keyservers
PGP keyservers (like keys.openpgp.org, keyserver.ubuntu.com) act as public directories where users upload their keys. Anyone can search by email address or key ID. However, keyservers have problems:
- Anyone can upload keys claiming any email address
- Keys accumulate spam and can't be reliably deleted
- No built-in verification that
bob@example.comactually controls the uploaded key
Web Key Directory (WKD)
WKD solves the trust problem by letting domain owners publish keys via HTTPS. When you email alice@example.org, your client checks https://openpgpkey.example.org/.well-known/openpgpkey/example.org/hu/[hash]. If the domain administrator placed Alice's key there, you retrieve it with DNS+HTTPS security guarantees.
This is analogous to how HTTPS certificates prove domain ownership.
DANE and OPENPGPKEY
DANE (DNS-Based Authentication of Named Entities) uses DNSSEC-signed DNS records to publish keys directly. An OPENPGPKEY DNS record type can contain a user's public key, cryptographically signed by the domain's DNS infrastructure. This provides stronger guarantees than plain keyservers but requires DNSSEC deployment.
Modern Approaches
Contemporary clients try multiple methods in sequence: check WKD first (most trustworthy), fall back to autocrypt headers in previous emails, then query keyservers as a last resort.
Key Takeaway: Key discovery has evolved from unverified public keyservers to domain-controlled WKD and DANE mechanisms that leverage existing trust infrastructure (HTTPS, DNSSEC) to prove key ownership.