Bug #15143

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

Added by intrigeri 2018-01-03 08:11:49 . Updated 2018-01-05 08:52:56 .

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

100%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

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?

Subtasks

History

#1 Updated by anonym 2018-01-04 17:42:17

  • 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 commit: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 2018-01-04 19:17:41

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

#3 Updated by intrigeri 2018-01-05 08:52:56

  • 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!