Project

General

Profile

Bug #15143

Tails 3.3 and 3.2 UDFs are signed with a subkey that expires on 2018-01-11

Added by intrigeri over 1 year ago. Updated over 1 year ago.

Status:
Resolved
Priority:
High
Assignee:
-
Category:
-
Target version:
Start date:
01/03/2018
Due date:
% Done:

100%

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

Description

I think they should instead have been signed with your new subkey, so Tails Upgrader can still do its job after 2018-01-11.

Can you please fix that?

Associated revisions

Revision 1bc81e19 (diff)
Added by anonym over 1 year ago

Resign "supported" UDFs with one of the new subkeys.

The subkey used for the old signatures expires in a week, on
2018-01-11.

Will-fix: #15143

History

#1 Updated by anonym over 1 year ago

  • Status changed from Confirmed to In Progress
  • Assignee changed from anonym to intrigeri
  • % Done changed from 0 to 50
  • QA Check set to Ready for QA

So are 1.0~test and 1.1~test, used by the automated test suite, so I resigned them too.

intrigeri, please make sure I didn't fuck up in 1bc81e19553ffe105d94736a479256321fc44779. Once it was live on our website, I booted Tails 3.3 and verified that its update check succeeded, so it looks good to me.

#2 Updated by intrigeri over 1 year ago

  • Target version changed from Tails_3.5 to Tails_3.4

#3 Updated by intrigeri over 1 year ago

  • Status changed from In Progress to Resolved
  • Assignee deleted (intrigeri)
  • % Done changed from 50 to 100
  • QA Check changed from Ready for QA to Pass

LGTM, thanks!

Also available in: Atom PDF