Project

General

Profile

Feature #14484

Update our OpenPGP keys in 2018

Added by intrigeri about 2 months ago. Updated about 2 months ago.

Status:
Confirmed
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
09/01/2017
Due date:
% Done:

0%

QA Check:
Feature Branch:
Type of work:
Sysadmin
Blueprint:
Easy:
Affected tool:

Description

What we're supposed to do each year:

  • Bump the master key's expiration date by 1 year.
  • Generate a new signing subkey for each RM, and move it onto new smartcards (the old ones are still needed to keep the previous subkey during the transition period).
  • If needed, generate and split a revocation certificate for our signing key. See internal.git for details.
  • Create a ticket about updating our OpenPGP keys next year.

To be done at the summit during northern hemisphere summer.


Subtasks

Feature #14582: Ensure we have enough OpenPGP smartcard/GNUK hardware for our 2018 keys updateConfirmedanonym


Related issues

Related to Tails - Feature #11747: Update our OpenPGP keys in 2017 Resolved 08/30/2016

History

#1 Updated by intrigeri about 2 months ago

#2 Updated by intrigeri about 2 months ago

  • Description updated (diff)

Let's try not to forget the master key next year..

Also available in: Atom PDF