Skip to content

Post-Quantum Cryptography

GpgFrontend lets you make and use post-quantum keys with a few clicks. You do not need the command line. This page explains in plain words what that means, why it might matter to you, and how to make your first one.

Today’s encryption is safe because breaking it would take even the fastest normal computer billions of years. The math is just too hard. Think of it as a lock that no machine on Earth can pick.

Quantum computers are a new and very different kind of computer. A big enough one could do that hard math quickly, and pick today’s locks. Machines that powerful don’t exist yet. But there is a catch:

Someone can copy your locked messages today, save them, and wait. When a strong quantum computer finally arrives, they unlock everything they saved, even messages from years ago.

This is called “harvest now, decrypt later.” So the real question isn’t “can anyone read this today?” It’s “does this need to stay secret for many years?”

If the answer is yes, it makes sense to start using new, quantum-proof encryption now, before quantum computers catch up. This kind of encryption is called post-quantum. NIST, the standards office of the United States, has approved a new set of post-quantum algorithms. OpenPGP is starting to use them.

GpgFrontend offers the new NIST-approved post-quantum algorithms. Like normal keys, they do one of two jobs. Some are for encryption (locking messages). Some are for signing (proving a message is really from you).

A quick plain-words guide:

ML-KEM

Once called Kyber. For encryption. GpgFrontend always pairs it with a classic algorithm. A pair like this is called a hybrid. Your protection is then never weaker than today’s, even if one of the two is later found to have a flaw.

ML-DSA

Once called Dilithium. For signing, also paired with a classic algorithm.

SLH-DSA

Once called SPHINCS+. Also for signing. It is built on a very simple, well-trusted idea (hashing). This makes it the most cautious choice.

All of them need the newer version 6 (v6) key format. GpgFrontend picks v6 for you when you choose a post-quantum option.

The table below lists the exact options for reference. The last column shows the oldest engine version that can make each one.

Algorithm OpenPGP Type Purpose Engine support
ML-KEM-768 + X25519 Hybrid KEM Encryption GnuPG 2.5.0 rPGP 0.1.2
ML-KEM-1024 + X448 Hybrid KEM Encryption GnuPG 2.5.0 rPGP 0.1.2
ML-DSA-65 + Ed25519 Hybrid sign Signing rPGP 0.1.2
ML-DSA-87 + Ed448 Hybrid sign Signing rPGP 0.1.2
SLH-DSA-SHAKE-128S Hash-based Signing rPGP 0.1.2
SLH-DSA-SHAKE-128F Hash-based Signing rPGP 0.1.2
SLH-DSA-SHAKE-256S Hash-based Signing rPGP 0.1.2
  1. Open the KeyPair Management window and click New Keypair. The Generate Key window opens.

  2. On the Identity step, fill in your name (and email, if you want), then click Continue.

  3. On the Key Type step, choose a post-quantum option:

    • The Hybrid encryption choice: messages to you are protected by ML-KEM as well as a classic algorithm. Signatures still use Ed25519.
    • Or open Advanced options, then Other profile, and pick a profile under the Post-Quantum heading. The Full PQC Hybrid profiles also use ML-DSA for signing.
    • Or turn on Expert Mode. The step is then called Key Details. Pick an Algorithm under the Post-Quantum heading. For encryption, choose ML-KEM for the subkey. For signing, choose ML-DSA or an SLH-DSA option for the primary key.

    If you do not see a choice, the active engine cannot make it. Most of these options need the rPGP engine.

  4. Click Continue. On the Validity & Protection step, choose how long the key is Valid for, then click Continue again. (In Expert Mode, you set Expires for each key on the Key Details step instead.)

  5. On the Review step, check the details and click Generate.

In Expert Mode, the Key format choice is locked to v6 while a post-quantum algorithm is selected.

That’s it. You now hold a post-quantum OpenPGP key.

Encrypt to Post-Quantum and Classic Keys Together

Section titled “Encrypt to Post-Quantum and Classic Keys Together”

You may pick some recipients with post-quantum keys and some with classic keys in the same message. GpgFrontend then shows a warning called Mixed Recipient Types.

Here is why. The message is locked once, and every recipient gets a copy of the same lock. If someone can break a classic recipient’s key, they can read the whole message. So the post-quantum protection does not hold for that message.

  • Click Cancel to go back. Then encrypt one message for the post-quantum recipients and a separate one for the others.
  • Click Encrypt Anyway if that risk is fine for you.