Project

General

Profile

ReleaseKey » History » Version 12

Wolfgang Wiedmeyer, 03/06/2017 01:41 PM
remove duplicate gpg --recv-key entry

1 7 Paul Kocialkowski
h1. Replicant release key
2 1 Paul Kocialkowski
3
The current Replicant release key expires: 2024-01-17 and has fingerprint:
4
<pre>
5 5 Paul Kocialkowski
E776 092B 052A DC91 FDD1 FD80 16D1 FEEE 4A80 EB23
6 1 Paul Kocialkowski
</pre>
7
8
h2. Retrieving the Replicant release key
9
10
h3. From a key server 
11
12 5 Paul Kocialkowski
You can retrieve our signing key from a public key server and import it to your GPG keyring using:
13 12 Wolfgang Wiedmeyer
14 9 Loic Dachary
<pre>
15 10 Wolfgang Wiedmeyer
gpg --recv-key 16D1FEEE4A80EB23
16 1 Paul Kocialkowski
</pre>
17
18
h3. From our releases
19
20 8 Paul Kocialkowski
A copy of our signing key is shipped with every Replicant release, distributed with [[ReplicantImages|Replicant images]].
21 1 Paul Kocialkowski
Once downloaded, the key can be imported to your GPG keyring using:
22
<pre>
23 6 Paul Kocialkowski
gpg  --armor --import path/to/4A80EB23.asc
24 1 Paul Kocialkowski
</pre>
25
26
h2. Establishing a chain of trust
27
28
In order to establish a chain of trust, you are encouraged to retrieve our release key physically when meeting a trusted [[People|Replicant developer]] and sign it with your own key.
29 11 Wolfgang Wiedmeyer
30
You can see the signatures the release key is already signed with running:
31
32
<pre>
33
gpg --list-sigs 16D1FEEE4A80EB23
34
</pre>
35
36
If a key you already trust is among these signatures, a chain of trust is established between your key and the release key. However, this chain of trust is not as strong as the direct one you establish when you personally verify and sign the release key.