PGP Basics: Encrypt Messages Without a Central Server
PGP protects content, not the envelope. OpenPGP protects content and signatures, while normal email routing metadata remains exposed. A full fingerprint check over a second channel establishes key trust.
Data behind this diagram
| Surface | State | Reason |
|---|---|---|
| Message content | Protected | Encrypted to the recipient key |
| File content | Protected | Encrypted before transport or storage |
| Signature integrity | Protected | Detects alteration and control of the signing key |
| Email headers | Exposed | Normal routing metadata is outside OpenPGP content encryption |
| Recipient data | Exposed | Mail servers process addressing |
| Timing | Exposed | Transport timing remains observable |
| Server logs | Exposed | Transport systems can retain routing records |
Key points
- PGP lets you protect message content without trusting one company.
- Fingerprint checks matter more than keyserver convenience.
- PGP hides content, not the metadata around it.
Snapshot
- Standard
- OpenPGP
- Confirmed
- RFC
- Main risk
- Key trust
- Caution
- GnuPG
- Best for
- Confirmed
- Practice
- No
- Metadata
- Caution
- Model
Practical steps
- Entry 1
- Encrypting files before cloud backup.
- Entry 2
- Signing software releases or public statements.
- Entry 3
- Exchanging sensitive email when both parties can verify fingerprints.
- Entry 4
- Creating durable identity keys not tied to one platform.
Sources
Frequently Asked Questions
Is PGP still useful in 2026?
Yes. PGP still works for email, file encryption, software signing, and identity checks when both sides verify fingerprints and protect private keys. It does not hide metadata, and it is clumsier than Signal, but it remains one of the few decentralized options.
Does PGP hide who I talk to?
No. OpenPGP protects message content and signatures. Email headers, timing, recipient data, and server logs still expose metadata unless you add separate transport protection and keep identities compartmentalized.
What is the most important safety check?
Verify the full key fingerprint through a second channel before trusting a public key. Skip that step and you can encrypt to an attacker key without realizing it.