Feature #8737

Sign the UDFs and ISO image with our new signing key

Added by intrigeri 2015-01-19 14:52:10 . Updated 2015-04-01 12:52:52 .

Status:
Resolved
Priority:
Elevated
Assignee:
anonym
Category:
Target version:
Tails_1.3.2
Start date:
2015-01-19
Due date:
% Done:

100%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

More specifically:

  • The 1.3.2 ISO must be signed with our new signing key.
  • UDFs that apply to version 1.3 and greater must be signed with our new signing key.
  • UDFs that apply to versions strictly before 1.3, and their detached signature, must be left unchanged, and will still be signed with the old signing key, so that multi-steps upgrade paths still work until our old signing key expires.

Subtasks

Related issues

Blocked by Tails - Feature #8740: Transition to a new signing key, phase 2 Resolved 2015-01-19

History

#1 Updated by intrigeri 2015-01-19 16:17:58

#2 Updated by intrigeri 2015-02-08 19:29:37

#3 Updated by intrigeri 2015-02-08 19:29:51

  • blocked by Feature #8740: Transition to a new signing key, phase 2 added

#4 Updated by BitingBird 2015-03-26 03:52:10

This happened with 1.3.1, so I guess this is resolved?

#5 Updated by intrigeri 2015-03-26 06:54:20

  • Description updated

Updated the description. IMO it’s worth keeping it open for 1.3.2 so that it’s clearly documented what exactly shall be signed with what key.

#6 Updated by intrigeri 2015-04-01 12:52:02

  • Status changed from Confirmed to Fix committed
  • % Done changed from 0 to 100

#7 Updated by intrigeri 2015-04-01 12:52:52

  • Status changed from Fix committed to Resolved