Public key
You give this out. Others use it to lock messages for you and to check your signatures.
Every day you trust other people with private things: emails, files, backups, ID documents, and passwords. OpenPGP lets you protect those things yourself, so only the people you choose can read them. It works offline and needs no account.
New to OpenPGP, GPG, or PGP? This guide starts with the few ideas you really need. Extra detail is at the end, for when you want it.
OpenPGP lets you do two things:
People use it for secure email, protecting files and backups, locking files before uploading to cloud storage, sharing passwords with people they trust, and checking that downloaded software is genuine.
You have two keys that work as a pair:
Public key
You give this out. Others use it to lock messages for you and to check your signatures.
Private key
You keep this secret. You use it to unlock messages sent to you and to sign things.
Think of a mailbox. Your public key is the slot anyone can drop mail into. Your private key is the only key that opens it.
Keep your private key safe. If you lose it, you can’t unlock your data. If someone steals it, they can read your messages and sign things as you.
Encrypting (for privacy): You lock a message with the other person’s public key. Only their private key can unlock it.
Signing (for proof): You sign a message with your private key. Anyone can use your public key to check that it really came from you and wasn’t changed.
You can do both at once: lock a message and sign it. Then it is private, and the reader can check who sent it.
When you make a key, GpgFrontend asks for a few things: your name (an email address is optional), what kind of key you want, how long the key is valid, and a passphrase.
If you’re new, just accept the defaults GpgFrontend suggests. They are a safe choice.
Pick a strong passphrase (a long password for your key). It is your last line of defense. If someone copies your private key file, the passphrase stops them from using it.
A name and email on a key prove nothing. Anyone can make a key with any name. So before you trust someone’s public key, make sure it is really theirs.
The usual way is to compare the key’s fingerprint (a unique ID code) using a source you already trust: an official website, a signed release page, or in person.
If you use GpgFrontend Lite or an rPGP key database, your keys live in the app’s own storage. Always export and back them up after you create or import them.
You now know enough to begin. A good first path, in this order:
If you ever feel stuck, the FAQ answers the most common questions from new users.
You can stop above and start using GpgFrontend. The sections below add detail for when you’re curious or need it.
These names get mixed up a lot:
GpgFrontend can work with GnuPG or with rPGP. See Engines and Compatibility below.
A full OpenPGP key is made of a few parts:
This keeps your identity separate from everyday tasks. Using subkeys for daily work lowers the risk to your primary key. Advanced users keep the primary key offline and use only subkeys on their everyday devices. See Generate and Use Subkeys.
When you share your public key, you usually share an OpenPGP certificate. It can include:
Remember: trust is not automatic. A valid signature only proves that the signature matches the key. You still have to decide whether the key really belongs to the right person.
OpenPGP is a standard, not one single app. GnuPG, rPGP, Sequoia PGP, RNP, and others are different programs that follow it. They can usually work together when they use the same formats and algorithms, but this is not guaranteed. Newer features like OpenPGP v6 and post-quantum algorithms may not work with older tools.
An engine is the program that does the actual encryption work for GpgFrontend. GpgFrontend supports more than one engine:
GnuPG
The default, recommended engine for daily use. It works with the widest range of other tools.
rPGP
An experimental engine for trying newer OpenPGP features, including OpenPGP v6 and some post-quantum algorithms.
If you’re new, use the GnuPG engine unless you want to try the newer features.
Each key database opens with its own engine. You choose the engine of the built-in key database in Settings > Key Databases. See Key Database.