A public–private key pair consists of two mathematically related keys with different roles. The public key can be shared; its matching private key must stay secret. Together, they support communication without first sharing a secret key. section 14.2.2 section 14.2.3
The keys support two different goals:
- For confidentiality, the sender encrypts with the recipient’s public key, and the recipient decrypts with their private key. section 14.2.2
- For a verifiable signature, the sender uses their private key and the recipient checks it with the sender’s public key. section 14.2.2
A message for Bob
Alice encrypts a confidential message with Bob’s public key. Bob decrypts it with his private key, which he keeps confidential. section 14.2.2
Sharing a public key does not by itself prove who owns it. Public key infrastructure uses trusted authorities and digital certificates to link keys to verified identities, helping prevent an attacker from substituting a key. section 14.2.6
Compared with symmetric encryption, key pairs ease distribution and scale across users, but asymmetric encryption is slower and more resource-intensive. It is better suited to tasks such as key exchange and authentication than bulk data encryption. section 14.2.3
|
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
|
Compare how public and private keys serve confidentiality and non-repudiation. section 14.2.2






