Feature #8222: Transition to a new signing key

Feature #8222

Transition to a new signing key

Added by intrigeri 2014-11-05 14:58:37 . Updated 2015-03-23 02:01:43 .

Status:

Resolved

Priority:

Elevated

Assignee:

Category:

Target version:

Tails_1.3.1

Start date:

2014-11-05

Due date:

2015-01-15

% Done:

100%

Feature Branch:

Type of work:

Sysadmin

Blueprint:

Starter:

Affected tool:

Deliverable for:

Description

We decided during the summit 2014 to generate a new one once the switch to smartcards is done. After the switch we’ll split this new key again.

Subtasks

Feature #8739: Transition to a new signing key, phase 1

Resolved

100

Feature #8740: Transition to a new signing key, phase 2

Resolved

100

History

#1 Updated by intrigeri 2014-11-05 14:58:52

blocked by #8221 added

#2 Updated by intrigeri 2014-11-05 15:00:03

Type of work changed from Code to Sysadmin

#3 Updated by intrigeri 2014-11-05 15:00:25

blocks #8223 added

#4 Updated by intrigeri 2014-11-05 15:01:23

blocks #8224 added

#5 Updated by sajolida 2014-11-05 17:46:22

Can you explain a bit the rationale behind this? What are the reasons behind this change of signing key?

#6 Updated by intrigeri 2014-11-06 09:51:56

sajolida wrote:
> Can you explain a bit the rationale behind this? What are the reasons behind this change of signing key?

I’m merely converting summit decisions into tickets. See notes/signing_key_split.mdwn in the summit-2014 Git repo. The idea is that once we have safer practices to store and use our signing key, we should drop the old one that was used less safely.