Project

General

Profile

ReleaseKey » History » Version 23

Kurtis Hanna, 11/30/2020 11:48 PM
Clarified that GNUtoo's keys are from 0004 rc1 up to whatever the newest release is at the time

1 16 dl lud
h1. Release keys
2 1 Paul Kocialkowski
3 14 Wolfgang Wiedmeyer
h2. Which key for which Replicant version?
4
5 23 Kurtis Hanna
h3. From Replicant 6.0 0004 RC1 up to the Current Release
6 19 Denis 'GNUtoo' Carikli
7
Key ID: FB31DBA3AB8DB76A4157329F7651568F80374459
8
9
These images are signed with [[People#Denis-GNUtoo-Carikli|Denis 'GNUtoo' Carikli]]'s key and has the following fingerprint:
10
<pre>
11
FB31 DBA3 AB8D B76A 4157  329F 7651 568F 8037 4459
12
</pre>
13
14 18 Denis 'GNUtoo' Carikli
h3. Up to Replicant 6.0 0003
15 14 Wolfgang Wiedmeyer
16
Key ID: 5816A24C10757FC4
17
18 17 Denis 'GNUtoo' Carikli
These images are signed with [[People#Wolfgang-Wiedmeyer|Wolfgang Wiedmeyer]]'s key and has the following fingerprint:
19 1 Paul Kocialkowski
<pre>
20 14 Wolfgang Wiedmeyer
0F30 D1A0 2F73 F70A 6FEE  048E 5816 A24C 1075 7FC4
21
</pre>
22
23
h3. Replicant 4.2 and below
24
25
Key ID: 16D1FEEE4A80EB23
26
27
These images are signed with the Replicant release key which expires 2024-01-17 and has the following fingerprint:
28
<pre>
29 1 Paul Kocialkowski
E776 092B 052A DC91 FDD1 FD80 16D1 FEEE 4A80 EB23
30
</pre>
31
32 13 Wolfgang Wiedmeyer
h2. Retrieving the Replicant release key
33 1 Paul Kocialkowski
34 14 Wolfgang Wiedmeyer
In the following, @KEY_ID@ needs to be replaced with the right key ID from above.
35
36 5 Paul Kocialkowski
h3. From a key server (recommended)
37 12 Wolfgang Wiedmeyer
38 9 Loic Dachary
You can retrieve our signing key from a public key server and import it to your GPG keyring using:
39 1 Paul Kocialkowski
40 10 Wolfgang Wiedmeyer
<pre>
41 14 Wolfgang Wiedmeyer
gpg --recv-key KEY_ID
42 13 Wolfgang Wiedmeyer
</pre>
43 1 Paul Kocialkowski
44 21 Kurtis Hanna
It sometimes is the case that certain keyservers have updated GPG keys while other keyservers have expired GPG keys or don't have them at all. In this situation, an alternate keyserver can be specified by adding a keyserver flag to the command:
45 20 Kurtis Hanna
46
<pre>
47
gpg --keyserver KEYSERVER_ID --recv-key KEY_ID
48
</pre>
49
50 22 Kurtis Hanna
For example, to get [[People#Denis-GNUtoo-Carikli|Denis 'GNUtoo' Carikli]]'s up to date public GPG key, you can use a command such as this:
51
52
<pre>
53
gpg --keyserver keys.gnupg.net --recv-key FB31DBA3AB8DB76A4157329F7651568F80374459
54
</pre>
55
56 1 Paul Kocialkowski
Errors may occur if GPG is not properly configured. Following a guide like "this":https://riseup.net/en/security/message-security/openpgp/best-practices should ensure that the key is retrieved securely.
57
58 8 Paul Kocialkowski
h3. From our releases
59 1 Paul Kocialkowski
60
A copy of our signing key is shipped with every Replicant release, distributed with [[ReplicantImages|Replicant images]].
61
Once downloaded, the key can be imported to your GPG keyring using:
62 6 Paul Kocialkowski
<pre>
63 14 Wolfgang Wiedmeyer
gpg  --armor --import path/to/KEY.asc
64 1 Paul Kocialkowski
</pre>
65
66
h2. Establishing a chain of trust
67
68 11 Wolfgang Wiedmeyer
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.
69 1 Paul Kocialkowski
70 11 Wolfgang Wiedmeyer
You can see the signatures the release key is already signed with running:
71
72 14 Wolfgang Wiedmeyer
<pre>
73 11 Wolfgang Wiedmeyer
gpg --list-sigs KEY_ID
74
</pre>
75 1 Paul Kocialkowski
76 20 Kurtis Hanna
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.