Project

General

Profile

Feature #8731

Feature #8222: Transition to a new signing key

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

Have both our new and old signing keys in the ISO and the user's keyring

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:

Description

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


Related issues

Blocks Tails - Feature #8732: Have Tails Upgrader trust both the old and new signing keys Resolved 01/19/2015

Associated revisions

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

Import the new Tails signing key.

It's signed by four people whose key is in the Debian keyring.

Closes: #8729, #8731.

History

#1 Updated by intrigeri about 5 years ago

  • Blocks Feature #8732: Have Tails Upgrader trust both the old and new signing keys added

#2 Updated by intrigeri about 5 years ago

  • Subject changed from Have both our new and old signing keys in the ISO to Have both our new and old signing keys in the ISO and the user's keyring

#3 Updated by intrigeri about 5 years ago

  • Private changed from Yes to No

#4 Updated by intrigeri about 5 years ago

  • Parent task changed from #8222 to #8739

#5 Updated by intrigeri about 5 years ago

  • Blocks deleted (Feature #8732: Have Tails Upgrader trust both the old and new signing keys)

#6 Updated by intrigeri about 5 years ago

  • Blocks Feature #8732: Have Tails Upgrader trust both the old and new signing keys added

#7 Updated by Tails almost 5 years ago

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

Applied in changeset commit:736cab76438e988097b99c67fabf03cc102eb1db.

Also available in: Atom PDF