Public key cryptography, also called asymmetric encryption, uses two related but different keys. A public key can be shared openly; its matching private key must be kept secret. This lets people communicate securely over an untrusted network without first sharing a secret key. section 14.2 section 14.2.2
Sending a confidential message
Suppose a coworker wants to send you a message that only you can read. They encrypt it with your public key, and you decrypt it with your private key. Anyone may obtain your public key, but that does not give them your private key. It also does not prove who sent the message: anyone could have used your public key. section 14.2.2
Which key is used depends on the goal:
- Confidentiality: the sender encrypts with the recipient’s public key; the recipient decrypts with their private key. section 14.2.2
- Proof of origin: the sender signs with their private key; others verify the signature with the sender’s public key. Digital signatures also help detect changes to the message. section 14.2.2 section 14.5
|
Property
|
Method
|
|
Confidentiality
|
• Sender
encrypts with the receiver's public key
• Receiver
decrypts with their own private key
|
|
Non-repudiation
|
• Sender signs
with their own private key
• Receiver
verifies with the sender's public key
|
This comparison keeps the two key-use patterns separate: encrypt for confidentiality, sign for proof of origin. section 14.2.2
Compared with symmetric encryption, which requires both parties to possess the same secret key, public key cryptography makes key distribution easier and scales better as more people communicate. The trade-off is speed: asymmetric methods require more processing power and are less practical for encrypting large amounts of data. They are especially useful for secure key exchange and authentication. section 14.2.3
Keys across an organization
If every pair of 100 employees needed its own shared secret, they would need 4,950 symmetric keys. With asymmetric cryptography, each employee would instead need one public–private key pair. The comparison illustrates why distributing keys matters in a growing organization. section 14.2.3
A public key is useful only if it really belongs to the claimed owner. An attacker who substitutes their own key could impersonate someone and intercept communications. Public key infrastructure (PKI) addresses this trust problem through digital certificates that link public keys to verified identities. Private keys also need protection: if one is compromised, an attacker may decrypt messages or forge signatures. section 14.2.6





