Bug #14927
deb.tails.boum.org archive signing key needs to be updated
100%
Description
It expires on 2018-01-25. In theory that’s after 3.4 so we could update it in 3.4, but let’s do this in 3.3 to be on the safe side.
This requires a little bit of sysadmin work + pushing the updated key to tails.git.
Subtasks
Related issues
Blocks Tails - |
Resolved | 2017-06-29 | |
Blocks Tails - Feature #13242: Core work: Sysadmin (Maintain our already existing services) | Confirmed | 2017-06-29 |
History
#1 Updated by intrigeri 2017-11-07 12:07:03
- blocks
Feature #13244: Core work 2017Q4: Foundations Team added
#2 Updated by intrigeri 2017-11-07 12:07:15
- blocks Feature #13242: Core work: Sysadmin (Maintain our already existing services) added
#3 Updated by intrigeri 2017-11-07 12:21:20
- Status changed from Confirmed to In Progress
Applied in changeset commit:79fff86f1ecdaf2b6fa0e76790216ab464fef6c5.
#4 Updated by intrigeri 2017-11-07 12:22:32
- % Done changed from 0 to 50
- QA Check set to Ready for QA
Updated private key in puppet-tails_secrets_apt
, pubkey in puppet-tails
and tails.git (master then merged to stable, testing & devel). Let’s see how it goes during the next Jenkins test suite runs.
#5 Updated by intrigeri 2017-11-07 15:29:25
- Assignee changed from intrigeri to anonym
The relevant scenario passed in https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/1019/console.
anonym, I already pushed (as said above) but please check that I didn’t do anything crazy: only the expiration date should have been bumped.
#6 Updated by anonym 2017-11-11 14:46:16
- Status changed from In Progress to Fix committed
- Assignee deleted (
anonym) - % Done changed from 50 to 100
- QA Check changed from Ready for QA to Pass
LGTM.
#7 Updated by anonym 2017-11-15 11:33:40
- Status changed from Fix committed to Resolved