11 KiB
A high-level view
Why OpenPGP?
OpenPGP is a widely recognized IETF-standardized set of cryptographic operations. It is broadly used in securing communications, for example, in encrypted text messages and email, and enjoys a vast ecosystem of libraries, tools, and community support forums. Moreover, its robustness and versatility has made OpenPGP a security choice for other use cases in which encryption is important. These include file transfer applications, password managers, and secure data storage.
There are other compelling reasons for why you might consider using OpenPGP in your project:
-
Decentralized trust model: OpenPGP's decentralization defines mechanisms for authentication that allow individuals and entities to create and manage their own cryptographic identities. Unlike centralized trust models, decentralized trust models empower individuals and entities to manage their own identities, fostering a community-driven web of trust instead of relying on a centralized authority, thus reducing single points of failure.
-
End-to-end encryption: OpenPGP provides a robust framework for implementing end-to-end encryption. Content remains confidential, verifiable, authenticated, and protected against unauthorized access, even when the communication channel itself might be otherwise compromised. Encryption is crucial in a myriad of scenarios, particularly when transmitting sensitive information such as financial data, personal identification information, or proprietary business data.
-
Anonymity and pseudonymity: In sensitive and volatile situations where identity protection is crucial, OpenPGP can be used to provide a level of anonymity or pseudonymity that helps protect user identities. For example, OpenPGP has been used alongside other privacy tools, such as Tor and VPNs, to provide secure and anonymous communication for whistleblowers, human rights lawyers, activists in repressive regimes, and journalists, reducing their risks for retaliation and state violence.
-
Interoperability: OpenPGP is a a well-structured and standardized protocol, widely adopted by various public and private entities but not tied to any particular vendor's technology. It supports all major operating systems, like Windows, macOS, GNU/Linux, Android, and iOS. Because of standardization, wide adoption, cross-platform compatibility, and adaptability, OpenPGP's interoperability significantly contributes to reducing development time, costs, and technical hurdles.
A very brief history
The OpenPGP standard has evolved over time, and remains under active development.
(Also see https://www.openpgp.org/about/history/)
Pretty Good Privacy (PGP)
The origins of OpenPGP can be traced back to Pretty Good Privacy (PGP), a software program written by Phil Zimmermann and first released in 1991.
The original PGP software played a role in the political struggles sometimes referred to as the "Crypto Wars" (also see "Crypto: How the Code Rebels Beat the Government Saving Privacy in the Digital" (2002), which includes some of PGP's history).
The original PGP software was never under a Free Software license, despite being widely published. PGP's ownership has changed over the years, and [PGP's scope and suite of products have expanded] (https://en.wikipedia.org/wiki/Pretty_Good_Privacy#PGP_Corporation_encryption_applications).
Standardizing OpenPGP
While PGP was first developed as commercial software, the owner at the time, PGP Inc., started a standardization effort with the IETF, first publishing RFC 1991 "PGP Message Exchange Formats" in August 1996.
In July 1997, a process to produce an open standard under the then new name OpenPGP was started, resulting in RFC 2440 "OpenPGP Message Format", published November 1998. RFC 2440 describes OpenPGP version 3.
The name OpenPGP can be used freely by implementations, unlike the name PGP, which is a registered trademark).
GnuPG, an early Free Software implementation
First released 1997-12-20 by Werner Koch, a German computer programmer, GNU Privacy Guard (GnuPG) is a free and open-source implementation of the OpenPGP standard.
GnuPG was a major early implementation of OpenPGP. Over the years, the importance of GnuPG has grown significantly as it became a foundational tool for email security, software signing, and more. It played an important (and successful) role in the release of NSA documents by Edward Snowden.
Because the GnuPG program binary is called "gpg," "GnuPG" and "gpg" are often used interchangeably.
Move this to an issue:
The following statement does not make sense here in the history part.
: The terms "pgp key" and "gpg key" are sometimes used. Since PGP and GnuPG are just two of many existing OpenPGP implementations, the proper term is "OpenPGP key" (or "OpenPGP certificate", more on that [later](certificates_chapter)).
The OpenPGP version 4 era
OpenPGP version 4
In 2007, the IETF published RFC 4880, which defined version 4 of the OpenPGP standard. At this time, version 4 is the most commonly used version.
Multiple major implementations
Today, multiple implementations of OpenPGP play important roles:
- Proton Mail, which provides email encryption services for a large number of users, uses and maintains OpenPGP.js as well as GopenPGP, an OpenPGP wrapper library written in golang.
- The Mozilla Thunderbird email software uses RNP, its C++ implementation of OpenPGP.
- The RPM Package Manager software includes an OpenPGP backend based on Sequoia PGP, a modern OpenPGP implementation written in Rust. The Fedora operating system, Fedora Linux 38, uses Sequoia PGP in rpm.
The road ahead
Let's insert a line about v5.
OpenPGP version 6
As of this writing (in 2023), version 6 of OpenPGP is approaching publication as an RFC. The IETF OpenPGP working group is focused on updating the cryptographic mechanisms, adding new algorithms, and the deprecation of obsolete algorithms.
This document describes OpenPGP version 6, while pointing out differences to previous versions that are relevant to application developers.
Significant support for OpenPGP version 6 has already been achieved for multiple implementations, including:
Post-quantum cryptography in OpenPGP
There is ongoing work to standardize and add support for post-quantum public-key algorithms in OpenPGP. This project is funded by the german "BSI". Goals include adding support for post-quantum cryptography to Thunderbird and GnuPG. A presentation was given at IETF 113.
Concepts
Certificates and keys in OpenPGP
OpenPGP revolves fundamentally around the concept of cryptographic keys.
In this framework, bare cryptographic keys are combined with additional metadata to form what are known as "OpenPGP certificates." These certificates are relatively complex data structures, also commonly referred to as "OpenPGP keys."
An OpenPGP certificate is dynamic, evolving over time as components are added, expire, or are marked as invalid.
For detailed information on structure and handling, read our chapters on OpenPGP certificates" and private keys.
Beyond the basics, managing certificates, as well as understanding their authentication and trust models, are crucial topics. Though this document will only briefly touch on these aspects, they constitute an integral part of working with OpenPGP.
High-Level operations
With OpenPGP it's possible to:
- Encrypt and Decrypt Messages
- Sign and Verify Data
- Issue and examine Statements about Keys and Identities (to perform CA-like functionality)
Building blocks
To perform these high-level operations, a set of established cryptographic mechanisms are used as building blocks, and combined into OpenPGP's format, which additionally deals with identities and their verification.
(interop_section)=
Interoperability
OpenPGP was standardized in 1997 to encourage development of interoperable implementations. This has already been a success early on, but in recent years, there has been much development of new implementations.
Historically, interoperability has only been tested in an adhoc manner. Since 2019, the Sequoia project is maintaining and operating the "OpenPGP interoperability test suite", for more rigorous and systematic testing. The test suite has identified numerous issues.
Zooming in: Internal structure of OpenPGP data
OpenPGP data is internally structured as "packets." We'll look into examples of this internal structure throughout the following chapters.
Getting familiar with the internal format of OpenPGP data is a good way to get familiar with the RFC, and it may also come in handy for debugging issues.
Gaining some familiarity with the internal structure of OpenPGP data will also help us to read the OpenPGP RFC, which describes the internal structure of OpenPGP packets in full detail.
(Most of the time, however, we will look at OpenPGP artifacts at a higher level of abstraction.)