CACrown ArchivesThe cinema collection
Menu
Research dossier · General Reference

GNU Privacy Guard

complete implementation of the OpenPGP and S/MIME standards

Cross-disciplinary reference desk with index cards, atlas, dictionary and catalogue
General referenceInterpretive dossier study · Crown Archives visual atlas
Record originEnglish Wikipedia
Text licenseCC BY-SA 4.0
Source revisionAug 26, 2026
Entity authorityQ223204 ↗
Source-derived summary

GNU Privacy Guard (GnuPG or GPG) is a free-software replacement for Symantec's cryptographic software suite PGP. The software is compliant with the now obsoleted RFC 4880, the IETF standards-track specification of OpenPGP. Modern versions of PGP are interoperable with GnuPG and other OpenPGP v4-compliant systems.

November 2023 saw two drafts aiming to update the 2007 OpenPGP v4 specification (RFC4880), ultimately resulting in the RFC 9580 standard in July 2024. The proposal from the GnuPG developers, which is called LibrePGP, was not taken up by the OpenPGP Working Group and future versions of GnuPG will not support the current version of OpenPGP.

GnuPG is part of the GNU Project and received major funding from the German government in 1999.

Overview

GnuPG is a hybrid-encryption software program because it uses a combination of conventional symmetric-key cryptography for speed, and public-key cryptography for ease of secure key exchange, typically by using the recipient's public key to encrypt a session key which is used only once. This mode of operation is part of the OpenPGP standard and has been part of PGP from its first version.

The GnuPG 1.x series uses an integrated cryptographic library, while the GnuPG 2.x series replaces this with Libgcrypt.

GnuPG encrypts messages using asymmetric key pairs individually generated by GnuPG users. The resulting public keys may be exchanged with other users in a variety of ways, such as Internet key servers. They must always be exchanged carefully to prevent identity spoofing by corrupting public key ↔ "owner" identity correspondences. It is also possible to add a cryptographic digital signature to a message, so the message integrity and sender can be verified, if a particular correspondence relied upon has not been corrupted.

Editorial summary

The public source identifies “GNU Privacy Guard” as complete implementation of the OpenPGP and S/MIME standards. This brief keeps that definition visible, then builds a research path around Privacy, Guard and complete.

Editorial reviewA concise reference frame for defining the subject, testing terminology and identifying the institution closest to the evidence. The current lead gives the account dated anchors—2023, 2007, 2024, 1999—that can be checked directly. The authority record carries competing date values—1997-12-20, 1997—which should remain separate until their references and qualifiers are resolved. Its value is orientation rather than verdict, with Privacy, Guard and complete providing the first useful test.
Editorial analysis

Why this record matters

A short description can identify a subject without explaining its stakes. For “GNU Privacy Guard”, the useful work is to connect “complete implementation of the OpenPGP and S/MIME standards” to the records capable of establishing context and consequence.

Evidence profile

Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated Aug 26, 2026. The linked authority identifier is Q223204. 3 of 4 selected statements include explicit references; 2 carry qualifiers and 2 use preferred rank. The first chronological checks are 2023, 2007, 2024 and 1999.

Critical limits

Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.

How to read it

Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.

Best used for
  • Subject orientation
  • Search vocabulary
  • Locating named sources
Verify next

The closest primary source, responsible institution and strongest cited specialist reference.

Three-step research path

  1. Establish the record: confirm the title “GNU Privacy Guard”, its source revision and the description used here.
  2. Expand the search: follow GNU Privacy Guard primary sources, GNU Privacy Guard archive and Privacy research across catalogues and specialist indexes.
  3. Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.

Questions for further research

  1. Which source most directly establishes the central claim about “GNU Privacy Guard”?
  2. Which institution is responsible for the underlying evidence?
  3. What terminology or title could unlock a more precise catalogue search?
Subject index

Search terms from this dossier

Source & attribution

This entry incorporates text from “GNU Privacy Guard” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.