Project

General

Profile

Bug #16420

Update the deb.tails.boum.org archive signing key

Added by intrigeri 15 days ago. Updated about 16 hours ago.

Status:
Fix committed
Priority:
High
Assignee:
-
Category:
Infrastructure
Target version:
Start date:
02/05/2019
Due date:
% Done:

100%

QA Check:
Pass
Feature Branch:
bugfix/16420-update-tails-apt-key
Type of work:
Sysadmin
Blueprint:
Starter:
Affected tool:

Description

It expires on 2019-05-01 (spotted by our test suite).

High prio as this makes the output of our CI less useful.


Related issues

Blocks Tails - Feature #13242: Core work 2017Q4 → 2019Q2: Sysadmin (Maintain our already existing services) Confirmed 06/29/2017

Associated revisions

Revision 5a7a43c2 (diff)
Added by bertagaz about 19 hours ago

Update tails' apt GnuPG key expiration.

Refs: #16420

Revision 05c7bc93
Added by intrigeri about 16 hours ago

Merge remote-tracking branch 'origin/bugfix/16420-update-tails-apt-key' into stable (Fix-committed: #16420)

History

#1 Updated by intrigeri 15 days ago

  • Blocks Feature #13242: Core work 2017Q4 → 2019Q2: Sysadmin (Maintain our already existing services) added

#2 Updated by intrigeri 15 days ago

(Assigning to bertagaz as the problem started during his shift; nobody filed a ticket about it back then but we got plenty of notifications on the -rm@ list, to which bertagaz is subscribed.)

#3 Updated by intrigeri 6 days ago

@bertagaz, what's your plan on this front? Do you need help?

#4 Updated by bertagaz 6 days ago

intrigeri wrote:

@bertagaz, what's your plan on this front? Do you need help?

Nop, I'll tackle that today or tomorrow.

#5 Updated by intrigeri 6 days ago

Nop, I'll tackle that today or tomorrow.

Great! :)

#6 Updated by bertagaz about 18 hours ago

  • Status changed from Confirmed to In Progress

#7 Updated by bertagaz about 18 hours ago

  • Assignee changed from bertagaz to intrigeri
  • QA Check set to Ready for QA
  • Feature Branch set to bugfix/16420-update-tails-apt-key

intrigeri wrote:

Nop, I'll tackle that today or tomorrow.

Great! :)

Took a bit more time, but is now ready to be merged in the Tails main repo. Branch is based on stable and should be merged into stable and devel.

I've already updated it in our puppet manifests (in the tails and tails_secrets_apt modules) and deployed it on apt.lizard. Please have a look there also to see if I did not forget about something.

#8 Updated by intrigeri about 16 hours ago

  • Status changed from In Progress to Fix committed
  • % Done changed from 0 to 100

#9 Updated by intrigeri about 16 hours ago

Took a bit more time, but is now ready to be merged in the Tails main repo. Branch is based on stable and should be merged into stable and devel.

Thanks, merged. We'll see how it goes on Jenkins once it's back on track (see groente's email on -sysadmins@).

I've already updated it in our puppet manifests (in the tails and tails_secrets_apt modules) and deployed it on apt.lizard. Please have a look there also to see if I did not forget about something.

bertagaz, @reprepro-tagged-snapshots@apt hasn't the updated key. IIRC, just like reprepro, Puppet will initialize it correctly when setting up a new system but the pieces to update the key are missing. I guess that fetching from the keyservers should fix it. Maybe we should run parcimonie for this user too. But reprepro-time-based-snapshots@apt has the updated key, not sure why.

#10 Updated by intrigeri about 16 hours ago

@bertagaz, see previous comment.

#11 Updated by intrigeri about 16 hours ago

  • Assignee deleted (intrigeri)
  • QA Check changed from Ready for QA to Pass

Also available in: Atom PDF