Public-key cryptography

Public-key cryptography separates the information needed to protect a message from the information needed to recover or authenticate it. A public key can be published, whereas its mathematically related private key must remain confidential. Security depends on a computationally difficult problem, not on hiding the algorithms themselves.

The modern idea emerged in the 1970s. Whitfield Diffie and Martin Hellman described public-key concepts and a method for establishing a shared secret over an exposed channel in 1976.¹ The independently developed RSA scheme soon demonstrated both public-key encryption and signatures through integer factorization assumptions.² These developments changed cryptographic practice by reducing the need for separately delivered secret keys.

Public-key encryption protects confidentiality by allowing anyone with the recipient’s public key to transform plaintext into ciphertext that the corresponding private key can reverse. In practice, protocols usually encrypt a randomly generated symmetric session key with the public key, then use that session key for bulk data because symmetric encryption is faster.³

Digital signatures use the pair in the opposite functional direction: the signer computes a signature with the private key, and anyone holding the public key can verify it. A valid signature can provide origin authentication and integrity, but it does not by itself prove that a particular person controlled the key; that binding commonly comes from certificates and a public-key infrastructure. Hash functions are normally part of the signing process, rather than the entire message being signed directly.

Different public-key algorithms rely on different mathematical assumptions. RSA relies on properties associated with factoring large integers; elliptic-curve systems obtain comparable security with shorter keys; and finite-field or elliptic-curve Diffie–Hellman methods establish shared secrets rather than directly encrypting application data.³ Digital-signature standards include RSA, ECDSA, and EdDSA, with algorithm choice governed by protocol requirements and approved security profiles.

Transport Layer Security uses public-key mechanisms during its handshake to authenticate endpoints and establish symmetric traffic keys.⁴ Certificates, typically issued within a public-key infrastructure, associate a public key with a named subject. Secure deployment also requires protected private-key storage, sound randomness, certificate validation, key rotation, revocation procedures, and careful parameter selection.

Public-key cryptography is not a single operation and does not automatically solve every security problem. Encryption can provide confidentiality without authenticating the sender, while a signature can provide integrity and attribution without concealing the message. Hybrid encryption combines both public-key and symmetric methods, and authenticated encryption is still needed to detect tampering in the data channel.³

Key compromise has consequences beyond one message: an exposed private signing key may invalidate trust in an entire sequence of documents, while loss of a decryption key can make archived ciphertext permanently inaccessible. Forward secrecy limits the damage from later compromise by creating ephemeral session keys, a property supported by ephemeral Diffie–Hellman exchanges in modern protocols.⁴ Quantum computing is a longer-term concern because Shor’s algorithm threatens widely deployed factoring- and discrete-logarithm-based systems; standards bodies therefore study post-quantum replacements rather than treating larger conventional keys as a complete answer.⁵

Public key

The openly distributable component of a key pair, used for encryption, signature verification, or key establishment.

Private key

The secret component of a key pair, used for decryption, signing, or generating shared-key material.

Digital signature

A private-key-generated value that a corresponding public key can verify against data and its integrity.

Public-key infrastructure

The policies, certificates, authorities, software, and procedures used to manage public keys and their asserted identities.

Forward secrecy

A property in which compromise of a long-term private key does not reveal previously established session keys.