OpenPGP

OpenPGP is an open standard that describes a message (file) format originally used by the Pretty Good Privacy (PGP) program, initially developed by Phil Zimmermann in 1991.

Uses your system voice; voice and rate in settings.

≈ 8 min read

Cite, export and learn8 citation formats · 8 exports · lesson and quiz

Names in other languages

No names in other languages are held for this entry yet.

Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.

OpenPGP is an open standard that describes a message (file) format originally used by the Pretty Good Privacy (PGP) program, initially developed by Phil Zimmermann in 1991. A number of standard-track Request for Comment documents augment its functionality, one example being PGP/MIME which defines the use of OpenPGP in email via MIME.

OpenPGP's encryption can ensure the secure delivery of files and messages, as well as provide verification of who created or sent the message using a process called digital signing. Using OpenPGP for communication requires participation by both the sender and recipient.

OpenPGP can also be used to secure sensitive files when they are stored in vulnerable places like mobile devices or in the cloud. OpenPGP is on the Internet Standards Track and is under active development. Many e-mail clients provide OpenPGP-compliant email security as described in RFC 3156.

The current base specification is (July 2024), the successor to RFC 4880. RFC 9580 specifies a suite of required algorithms consisting of X25519, Ed25519, SHA2-256 and AES-128. In addition to these algorithms, the standard recommends X448, Ed448, SHA2-384, SHA2-512 and AES-256.

Beyond these, many other algorithms are supported. The additional specification (June 2026) defines Post-Quantum Cryptography in OpenPGP, based on ML-KEM composite public key encryption and ML-DSA composite public key signatures, both in combination with Elliptic Curve Cryptography (ECC), as well as SLH-DSA as a standalone public key signature scheme.

Design

(Open)PGP encryption uses a serial combination of hashing, data compression, symmetric-key cryptography, and finally public-key cryptography; each step uses one of several supported algorithms. Each public key is bound to a username or an e-mail address.

The first version of this system was generally known as a web of trust to contrast with the X.509 system, which uses a hierarchical approach based on certificate authority and which was added to OpenPGP implementations later. Current versions of OpenPGP include options through an automated key management server.

PGP fingerprint

A public key fingerprint is a fixed-length unique identifier of a public key. By comparing fingerprints, a recipient can validate that they have obtained the expected public key. A fingerprint such as C959 BDBA FA32 A2F8 9A15 3B67 8CFD E121 9796 5A9A can be printed on a business card.

Compatibility

As OpenPGP evolves, versions that support newer features and algorithms can create encrypted messages that older OpenPGP systems cannot decrypt, even with a valid private key. Therefore, it is essential that partners in OpenPGP communication understand each other's capabilities or at least agree on PGP settings. See § Version history below for a list of version codes.

Confidentiality

PGP can be used to send messages confidentially. For this, PGP uses a hybrid cryptosystem by combining symmetric-key encryption and public-key encryption. The message is encrypted using a symmetric encryption algorithm, which requires a symmetric key generated by the sender.

The symmetric key is used only once and is also called a session key. The message and its session key are sent to the receiver. The session key must be sent to the receiver so they know how to decrypt the message, but to protect it during transmission it is encrypted with the receiver's public key.

Only the private key belonging to the receiver can decrypt the session key and use it to symmetrically decrypt the message.

Digital signatures

PGP supports message authentication through digital signatures to verify whether a message was actually sent by the person or entity claimed to be the sender. The sender uses PGP to create a digital signature for the message with one of several supported public-key algorithms. To do so, PGP computes a hash, or digest, from the plaintext and then creates the digital signature from that hash using the sender's private key.

Web of trust

Both when encrypting messages and when verifying signatures, it is critical that the public key used to send messages to someone or some entity actually does 'belong' to the intended recipient. Simply downloading a public key from somewhere is not a reliable assurance of that association; deliberate (or accidental) impersonation is possible.

From its first version, PGP has always included provisions for distributing user's public keys in an 'identity certification', which is also constructed cryptographically so that any tampering (or accidental garble) is readily detectable. However, merely making a certificate that is impossible to modify without being detected is insufficient; this can prevent corruption only after the certificate has been created, not before.

Users must also ensure by some means that the public key in a certificate actually does belong to the person or entity claiming it. A given public key (or more specifically, information binding a user name to a key) may be digitally signed by a third-party user to attest to the association between someone (actually a user name) and the key.

There are several levels of confidence that can be included in such signatures. Although many programs read and write this information, few (if any) include this level of certification when calculating whether to trust a key.

The web of trust protocol was first described by Phil Zimmermann in 1992, in the manual for PGP version 2.0: The web of trust mechanism has advantages over a centrally managed public key infrastructure scheme such as that used by S/MIME but has not been universally used. Users have to be willing to accept certificates and check their validity manually or have to simply accept them.

No satisfactory solution has been found for the underlying problem.

Certificates

In the (more recent) OpenPGP specification, trust signatures can be used to support creation of certificate authorities. A trust signature indicates both that the key belongs to its claimed owner and that the owner of the key is trustworthy to sign other keys at one level below their own.

A level 0 signature is comparable to a web of trust signature since only the validity of the key is certified. A level 1 signature is similar to the trust one has in a certificate authority because a key signed to level 1 is able to issue an unlimited number of level 0 signatures.

A level 2 signature is highly analogous to the trust assumption users must rely on whenever they use the default certificate authority list (like those included in web browsers); it allows the owner of the key to make other keys certificate authorities. (Open)PGP versions have always included a way to cancel ('revoke') public key certificates.

A lost or compromised private key will require this if communication security is to be retained by that user. This is, more or less, equivalent to the certificate revocation lists of centralised PKI schemes. Recent OpenPGP versions have also supported certificate expiration dates.

The problem of correctly identifying a public key as belonging to a particular user is not unique to PGP. All public key/private key cryptosystems have the same problem, even if in slightly different guises, and no fully satisfactory solution is known.

OpenPGP's web-of-trust scheme at least leaves the decision as to whether or not to use its endorsement/vetting system to the user, while most other PKI schemes do not, requiring instead that every certificate attested to by a central certificate authority be accepted as correct.

See also

Autocrypt Email encryption Email privacy GNU Privacy Guard Gpg4win Key server (cryptographic) Privacy software Public-key cryptography S/MIME X.509

OpenPGP::SDK MIT Public Key Directory for Registration and Search List of public keyservers IETF OpenPGP working group OpenPGP Alliance

Text derived from https://en.wikipedia.org/w/index.php?oldid=1378868255 under CC BY-SA 4.0; modifications have been made.

Words in each sectionWeb of trustWeb of trustWeb of trust: 294 words294CertificatesCertificatesCertificates: 293 words293ConfidentialityConfidentialityConfidentiality: 119 words119DesignDesignDesign: 87 words87Digital signaturesDigital signaturesDigital signatures: 72 words72CompatibilityCompatibilityCompatibility: 58 words58PGP fingerprintPGP fingerprintPGP fingerprint: 49 words49See alsoSee alsoSee also: 20 words20
Words in each section. Measured from the stored article body; sections below the minimum are not plotted.

Provenance

snapshot enwiki-001378868255 · captured 2026-10-06 · ledger · version history

Cite this page as: encyclopegia.org, “OpenPGP”, snapshot enwiki-001378868255. https://encyclopegia.org/a/openpgp

Sources cited in this revision

32 named source(s) extracted from the cited revision. A source with no author is shown by its publication; nothing is invented.