Project

General

Profile

Actions

ReleaseKey » History » Revision 9

« Previous | Revision 9/27 (diff) | Next »
Loic Dachary, 10/22/2016 09:57 PM
update the --recv-key lines with alternate server explicitly set, in case a user has no default and is unfamilar with gpg and/or one of the server is down


Replicant release key

The current Replicant release key expires: 2024-01-17 and has fingerprint:

E776 092B 052A DC91 FDD1 FD80 16D1 FEEE 4A80 EB23

Retrieving the Replicant release key

From a key server

You can retrieve our signing key from a public key server and import it to your GPG keyring using:

gpg --keyserver keys.gnupg.net --recv-key 4A80EB23

or
gpg --keyserver pgp.mit.edu --recv-key 4A80EB23

From our releases

A copy of our signing key is shipped with every Replicant release, distributed with Replicant images.
Once downloaded, the key can be imported to your GPG keyring using:

gpg  --armor --import path/to/4A80EB23.asc

Establishing a chain of trust

In order to establish a chain of trust, you are encouraged to retrieve our release key physically when meeting a trusted Replicant developer and sign it with your own key.

Updated by Loic Dachary almost 6 years ago · 9 revisions locked

Also available in: PDF HTML TXT