Using GPG in the FSFE

GnuPG (GPG) is a system for guaranteeing the identity and privacy of e-mails (and data in general), based on Public-key cryptography and the OpenPGP standard.

Identity is guaranteed by digital signature, privacy is guaranteed by encryption. To digitally sign and encrypt your e-mail messages with GPG, you need your own GPG keypair, keep your GPG private key safe on your system, and distribute your GPG public key.

In this page you will find basic instructions to create your GPG key and use it in your FSFE-related communications.

If you are new to GPG, or want to know more, you can read an introduction at:

Install required software

To use GPG in your e-mail communication, you need to install:

Generate your GPG keypair

If you already have a GPG keypair, you can just add a new user-id to it (using your mail address). But if you prefer to create a separate GPG key to be only used for FSFE, that's fine too.

If you need to create your own keypair, follow these instructions:

Share your GPG key

Core team members, GA members and employees are supposed to send their public keys to other members in their respective teams so they can communicate securely with you. Volunteers of others teams could attach their keys to their messages or upload their key to keyservers.

  1. Find out your fingerprint, e.g. ABCDCD00386B3CB26BA123452704E4AB371E2E77, by having a look at the secret keys you own.

    gpg --list-secret-keys
  2. Export your public key to an ascii file; run
    gpg -a --export ABCDCD00386B3CB26BA123452704E4AB371E2E77 > yourkey.asc
  3. It is recommended to upload your key to a keyserver to enable others to fetch your key based on your fingerprint or GPG signature.
    gpg --send-key ABCDCD00386B3CB26BA123452704E4AB371E2E77
  4. Send the yourkey.asc file to,,, depending on your memberships.

You are encouraged to have your GPG key verified and signed by other FSFE team members or other GPG users; community meetings or FSFE-related events are usually a good occasion for it.

TechDocs/GPG (last edited 2018-07-25 10:41:53 by max.mehl)