End-to-End Encryption
Only sender and recipient can read content; intermediaries cannot. PGP and Signal-style messengers provide E2EE; HTTPS protects only to the server unless additional E2EE is used.
End-to-end encryption (E2EE) means content is encrypted on the sender’s side and decrypted only on the recipient’s; every intermediary — relays, servers, platform operators — sees ciphertext. PGP-encrypted messages and Signal-protocol messengers are the standard examples.
Why it matters on Tor
Tor hides network paths, and HTTPS to an onion service is encrypted to that service — but the operator of a market or forum can still read everything submitted to it. When two users communicate through such a platform, only an additional E2EE layer, classically PGP, keeps the platform itself, or anyone who later seizes its server, out of the conversation. This is why darknet communities treat sensitive unencrypted messages on any platform as exposed.
Limits
E2EE protects content, not metadata: who messaged whom and when may still be visible. It cannot fix compromised endpoints — malware on either side reads plaintext before encryption or after decryption. And usability failures, such as encrypting to the wrong key or skipping fingerprint verification, silently void the guarantee.
Category: Cryptography