| Internet-Draft | Persistent Symmetric Keys in OpenPGP | July 2023 |
| Huigens | Expires 11 January 2024 | [Page] |
This document defines new algorithms for the OpenPGP standard (RFC4880) to support persistent symmetric keys, for message encryption using authenticated encryption with additional data (AEAD) and for authentication with hash-based message authentication codes (HMAC). This enables the use of symmetric cryptography for data storage (and other contexts that do not require asymmetric cryptography), for improved performance, smaller keys, and improved resistance to quantum computing.¶
This note is to be removed before publishing as an RFC.¶
The latest revision of this draft can be found at https://twisstle.gitlab.io/openpgp-persistent-symmetric-keys/. Status information for this document may be found at https://datatracker.ietf.org/doc/draft-huigens-openpgp-persistent-symmetric-keys/.¶
Discussion of this document takes place on the OpenPGP Working Group mailing list (mailto:openpgp@ietf.org), which is archived at https://mailarchive.ietf.org/arch/browse/openpgp/. Subscribe at https://www.ietf.org/mailman/listinfo/openpgp/.¶
Source for this draft and an issue tracker can be found at https://gitlab.com/twisstle/openpgp-persistent-symmetric-keys.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 11 January 2024.¶
Copyright (c) 2023 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
The OpenPGP standard [RFC4880] has supported symmetric encryption for data packets using session keys since its inception, as well as symmetric encryption using password-derived keys. This document extends the use of symmetric cryptography by adding support for persistent symmetric keys which can be stored in a transferable private key, and used to symmetrically encrypt session keys, for long-term storage and archival of messages. This document uses authenticated encryption with associated data (AEAD) as proposed by the OpenPGP crypto refresh [crypto-refresh].¶
The OpenPGP standard also supports the use of digital signatures for authentication and integrity but no similar symmetric mechanism exists in the standard. This document introduces hash-based message authentication codes (HMAC) as a symmetric counterpart to digital signatures, for long-term storage and archival of attestations of authenticity and certification.¶
Rather than introducing new packets for storing persistent symmetric keys, the existing Secret-Key packets are reused for this purpose. To indicate the type of keys, two algorithms (AEAD and HMAC) are registered, whose IDs can be used in the place of public-key algorithm IDs. To accommodate these additions, we propose renaming the Public Key Algorithms registry to Persistent Key Algorithms.¶
Similarly, we reuse the Signature packet for "symmetric signatures". For session keys encrypted with persistent symmetric keys, while a "Symmetric-Key Encrypted Session Key packet" exists, its semantics don't match our goals, as it's intended to encrypt the session key with a user-provided password, and doesn't offer a way to store a reference to a persistent key. Therefore, we reuse the "Public-Key Encrypted Session Key packet" instead, which does offer the desired semantics. Nevertheless, given this usage, the naming of these packets may be confusing, so we propose to rename them to "Password Encrypted Session Key packet" and "Key Encrypted Session Key packet", instead.¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. Any implementation that adheres to the format and methods specified in this document is called a compliant application. Compliant applications are a subset of the broader set of OpenPGP applications described in [RFC4880] and the OpenPGP crypto refresh [crypto-refresh]. Any [RFC2119] keyword within this document applies to compliant applications only.¶
When compared to asymmetric cryptography, symmetric cryptography can provide improved performance and equivalent security with smaller keys. In contexts that do not require asymmetric cryptography, such as secure data storage where the same user encrypts and decrypts data, symmetric cryptography can be used to take advantage of these benefits.¶
Additionally, asymmetric algorithms included in OpenPGP are vulnerable to attacks that might become possible on quantum computers [Shor]. Symmetric cryptography is also affected by quantum computing but to a lesser extent, which can be countered by using larger keys [Grover]. While the standardization of quantum-secure asymmetric cryptography in OpenPGP is ongoing [PQCinOpenPGP], and will be required to secure communications, there is a large body of existing messages encrypted with classical algorithms. Once persistent symmetric keys are available, these messages can be protected against future compromises efficiently by symmetrically re-encrypting the session key, and storing the message symmetrically encrypted for long-term storage and archival.¶
This document defines two new algorithms for use with OpenPGP, extending the table in section 9.1 of [crypto-refresh].¶
| ID | Algorithm | Public Key Format | Secret Key Format | Signature Format | PKESK Format |
|---|---|---|---|---|---|
| 64 | AEAD | sym. algo, seed hash [Section 4.1] | hash seed, key material | N/A | AEAD algo, IV, length, ciphertext [Section 4.3] |
| 65 | HMAC [RFC2104] | hash algo, seed hash [Section 4.2] | hash seed, key material | authentication tag [Section 4.4] | N/A |
These algorithm IDs can be used to store symmetric key material in Secret-Key Packets and Secret-Subkey packets (see section 5.5.3 of [crypto-refresh]). The AEAD algorithm ID can be used to store session keys encrypted using AEAD in PKESK packets (see section 5.1 of [crypto-refresh]). The HMAC algorithm ID can be used to store HMAC-based signatures in Signature packets (see section 5.2 of [crypto-refresh]).¶
As the secret key material is required for all cryptographic operations with symmetric keys, implementations SHOULD NOT use these algorithm IDs in Public-Key Packets or Public-Subkey Packets, and SHOULD NOT export Public-Key Packets from Secret-Key Packets holding symmetric key material.¶
The public key is this series of values:¶
The private key is this series of values:¶
The public key is this series of values:¶
The private key is this series of values:¶
Although not required by HMAC, to maintain compatibility with existing signature implementations, HMAC tags are produced from appropriately hashed data, as per section 5.2.4 of [crypto-refresh].¶
To reflect the usage of symmetric algorithms, we propose to rename Public-Key Encrypted Session Key Packet (Tag 1) to Persistent Key Encrypted Session Key Packet, and rename Symmetric-Key Encrypted Session Key Packet (Tag 3) to String-to-Key Encrypted Session Key Packet. These names reflect the semantics and intended use of the packets, as opposed to the cryptographic algorithms used.¶
Additionally, we propose to rename the Public Key Algorithms registry to Persistent Key Algorithms.¶
Security considerations are discussed throughout the document where appropriate.¶
IANA is requested to rename the "Public Key Algorithms" registry to "Persistent Key Algorithms", and add the entries in Table 1 to the registry.¶
IANA is requested to modify the "PGP Packet Types/Tags" registry as follows:¶
An initial version of this draft was written by Dan Ristea (Proton AG), with guidance from Dr Philipp Jovanovic (University College London).¶