Project

General

Profile

Feature #8732

Feature #8222: Transition to a new signing key

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

Have Tails Upgrader trust both the old and new signing keys

Added by intrigeri about 5 years ago. Updated almost 5 years ago.

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
-
Target version:
Start date:
01/19/2015
Due date:
% Done:

100%

Feature Branch:
Type of work:
Code
Blueprint:
Starter:
Affected tool:
Upgrader

Description

This needs to be done in 1.3, to ensure a smooth upgrade path to 1.3.1.


Related issues

Blocked by Tails - Feature #8731: Have both our new and old signing keys in the ISO and the user's keyring Resolved 01/19/2015

Associated revisions

Revision 23bf276b (diff)
Added by Tails developers almost 5 years ago

Have Tails Upgrader trust both the old (current) and new (future) Tails signing keys.

This will ensure a smooth transition when we sign the UDFs with the new signing
key once Tails 1.3.1 is out.

Closes: #8732

History

#1 Updated by intrigeri about 5 years ago

  • Blocked by Feature #8731: Have both our new and old signing keys in the ISO and the user's keyring added

#2 Updated by intrigeri about 5 years ago

  • Private changed from Yes to No

#3 Updated by intrigeri about 5 years ago

  • Blocked by deleted (Feature #8731: Have both our new and old signing keys in the ISO and the user's keyring)

#4 Updated by intrigeri about 5 years ago

  • Parent task changed from #8222 to #8739

#5 Updated by intrigeri about 5 years ago

  • Blocked by Feature #8731: Have both our new and old signing keys in the ISO and the user's keyring added

#6 Updated by Tails almost 5 years ago

  • Status changed from Confirmed to Resolved
  • % Done changed from 0 to 100

Applied in changeset commit:d5aee9f1036e0c6ce88523a67e55a792cec71697.

Also available in: Atom PDF