GPG: a Fedora primer

GPG, or GnuPG, refers to the Gnu Privacy Guard utility. GPG is a freely available implementation of the OpenPGP standard that was released by Werner Koch in 1999. The security and privacy of data and individuals is an important topic in modern culture. The OpenPGP standard allows GPG and other applications to work together to secure and protect your data.

This series will explain the basic fundamentals of GPG and take you step by step through using it. The OpenPGP standard includes the basic features of confidentiality, integrity, and non-repudiation. By supporting this standard, GPG provides all three features.


Confidentiality is the ability to keep contents of a file or message private. To provide confidentiality, GPG can convert the original contents of a file, called plaintext, to an encrypted version called ciphertext. This can help keep your files secure on a computer, removable drives, or when transmitted over the Internet. Think of it as using a secret code to write a letter. Even if the letter is intercepted and the envelope steamed open, the message cannot be read.

The example plaintext below is encrypted with the pass phrase “openme”. This is an example of a symmetric algorithm, where the same key is used for both encryption and decryption.

Plain text:
the quick brown fox
Encrypted text:

A future article in this series will cover email encryption with GPG.


Another function of GPG ensures the integrity of a file. This feature is used by the Fedora Project to help ensure the image you download is the one Fedora provides. In the case of Fedora, both a checksum and a signature are generated.

A checksum is a set of digits that represent data, such as a file. The checksum is generated by a special one-way mathematical algorithm. The algorithm cannot be reversed to discover the original data from the checksum. The algorithm is also designed to make it exceedingly difficult for two sets of data to generate the same checksum.

You will see this on the page that thanks you for downloading Fedora:

GnuPG Fedora Download

The text below is from the page you see when you click the Validate button on the page above. To verify this information and the image itself, follow the link for the instructions.

Hash: SHA256

# The image checksum(s) are generated with sha256sum.
SHA256 (Fedora-Workstation-netinst-x86_64-23.iso) = f38d1aca6211b6bbb2873a550f393d03866294e3e5094256feb4cd647c25a310
SHA256 (Fedora-Live-Workstation-x86_64-23-10.iso) = a91eca2492ac84909953ef27040f9b61d8525f7ec5e89f6430319f49f9f823fe
Version: GnuPG v1


The signature also provides integrity checking for the checksums. If the checksum values were to change, the signature would no longer match. After verifying the signature, the hash values can be used to compare to a checksum on the downloaded image file. If they are the same, you can be certain the image is not tampered with or corrupted.


Non-repudiation ensures that a person cannot deny signing a file or message. If you always sign your messages, someone receiving an unsigned message should suspect it is a fake. The non-repudiation process requires a more complex cryptographic system than the symmetric example shown earlier. Asymmetric or public-key cryptography makes this feature possible.

In a public-key system, each user has a public key, which they share as widely as possible; and a private key, which they protect as carefully as possible. Keyservers on the internet can collect and advertise public keys to make exchange of information easier.

To know if a signature is valid requires use of a keyserver to retrieve the public key for that signature. However, downloading or having a public key labeled as owned by someone does not prove the key actually belongs to that person.

For this reason, keys must be verified personally to be trusted. If you meet someone in person and verify their identity, you can trust their key. This “web of trust,” which will be discussed later in the series, allows you to trust a key from a person you haven’t personally met.


When confidentiality, integrity and non-repudiation are combined, authenticity is achieved. A file or message can be kept secret, verified to not have been tampered with, and verified to come from the specified source.

This is the beginning of a series of articles about using GPG. This series will show you how to create and maintain keys with GPG, understand and use the web of trust, understand and run key signing events, use GPG with email, and encrypt and sign files.

Image courtesy Bs0u10e0 – originally posted to Flickr as Savings

Fedora Contributor Community For Developers For System Administrators Using Software


  1. Kuba

    Thanks! Really nice article!

  2. I hope we are going to use GnuPG stable available as gpg2 for this series and not GnuPG Classic which is available as gpg on Fedora systems. gpg has much written about it but gpg2 specific posts are hard to find.

  3. David Liteman

    Excellent. I look forward to the lessons to further enhance my skills. I think these lessons should be mandatory in school for young people.

  4. Sean Hall

    Thanks. It’s a good start, but I’d really like to see this fleshed more.

  5. purpose

    there should be a date at the top for all these articles so a reader knows how old they are.

    • @purpose: The date appears in the author/about block at the bottom of the article, before comments, and also in the article metadata for news reader apps.

  6. How do we expect PGP to play a role in email communication moving forward? It’s important to have PGP keys verified by others to ensure a ring-of-trust, but it still seems that email programs are behind the times…

    And can we have a key verification booth at the next FUDCON? 🙂

  7. Like 10 years ago I used to have a GPG key and so. I’ve lost it long ago. Should I make a new one? May I use the same email?

  8. GPG is a freely available implementation of the OpenPGP standard that was released by Werner Koch in 1999. Where did you get this information?

Comments are Closed

The opinions expressed on this website are those of each author, not of the author's employer or of Red Hat. Fedora Magazine aspires to publish all content under a Creative Commons license but may not be able to do so in all cases. You are responsible for ensuring that you have the necessary permission to reuse any work on this site. The Fedora logo is a trademark of Red Hat, Inc. Terms and Conditions