ReleaseKey » History » Revision 13
Revision 12 (Wolfgang Wiedmeyer, 03/06/2017 01:41 PM) → Revision 13/29 (Wolfgang Wiedmeyer, 03/06/2017 03:13 PM)
h1. Replicant release key The current Replicant release key expires: 2024-01-17 and has fingerprint: <pre> E776 092B 052A DC91 FDD1 FD80 16D1 FEEE 4A80 EB23 </pre> h2. Retrieving the Replicant release key h3. From a key server (recommended) You can retrieve our signing key from a public key server and import it to your GPG keyring using: <pre> gpg --recv-key 16D1FEEE4A80EB23 </pre> 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. h3. From our releases A copy of our signing key is shipped with every Replicant release, distributed with [[ReplicantImages|Replicant images]]. Once downloaded, the key can be imported to your GPG keyring using: <pre> gpg --armor --import path/to/4A80EB23.asc </pre> h2. 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 [[People|Replicant developer]] and sign it with your own key. You can see the signatures the release key is already signed with running: <pre> gpg --list-sigs 16D1FEEE4A80EB23 </pre> 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.