Bug #10419

The OpenPGP key for deb.tails.boum.org will expire soon

Added by bertagaz 2015-10-25 06:35:51 . Updated 2015-11-03 11:28:41 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
Start date:
2015-10-25
Due date:
% Done:

100%

Feature Branch:
bugfix/10419-update-tails-APT-repo-key
Type of work:
Sysadmin
Blueprint:

Starter:
0
Affected tool:
Deliverable for:

Description

The test suite recently started to fail on the test of the deb.tails.boum.org package signing key.

It expires in less than 3 monthes:

pub   4096R/0xC7988EA7A358D82E 2012-02-04 [expires: 2016-01-25]
      Key fingerprint = 221F 9A3C 6FA3 E09E 182E  060B C798 8EA7 A358 D82E
uid                 [ unknown] deb.tails.boum.org archive signing key

Subtasks


Related issues

Related to Tails - Bug #8747: The OpenPGP key for deb.tails.boum.org will expire soon Resolved 2015-01-20

History

#1 Updated by bertagaz 2015-10-25 06:37:01

  • related to Bug #8747: The OpenPGP key for deb.tails.boum.org will expire soon added

#2 Updated by intrigeri 2015-10-26 04:50:22

  • Target version set to Tails_1.7

So it must be updated in Tais 1.8 to the latest. But we generally try to be nice to users who skipped a release, so including the updated key in 1.7 would be ideal.

#3 Updated by bertagaz 2015-10-26 05:34:54

intrigeri wrote:
> So it must be updated in Tais 1.8 to the latest. But we generally try to be nice to users who skipped a release, so including the updated key in 1.7 would be ideal.

Will try to do that for 1.7 as marked for this ticket, but can’t really promise I will, too much stuffs on my plate for today and coming days.

#4 Updated by bertagaz 2015-10-27 07:48:43

  • Status changed from Confirmed to In Progress

Applied in changeset commit:9e460350591f2f47303efc4485e3fd6268e0bf6c.

#5 Updated by bertagaz 2015-10-27 07:59:27

  • Assignee changed from bertagaz to intrigeri
  • % Done changed from 0 to 80
  • QA Check set to Ready for QA
  • Feature Branch set to bugfix/10419-update-tails-APT-repo-key
  • Starter set to No

Updated in a branch of the Tails repo, on the SKS keyservers, and deployed in our infra (including http://deb.tails.boum.org/key.asc)

#6 Updated by bertagaz 2015-10-27 11:22:56

bertagaz wrote:
> Updated in a branch of the Tails repo, on the SKS keyservers, and deployed in our infra (including http://deb.tails.boum.org/key.asc)

Test job #1 of the branch in Jenkins passed this step:

00:17:41.193   Scenario: The Tails Debian repository key is up-to-date                      # features/checks.feature:29
00:17:45.699     Given I have started Tails from DVD without network and logged in          # features/step_definitions/snapshots.rb:174
00:17:45.699     Then the shipped Debian repository key will be valid for the next 3 months # features/step_definitions/checks.rb:20

Seems to fix the issue there.

#7 Updated by intrigeri 2015-10-27 12:59:36

  • Assignee changed from intrigeri to anonym

> Updated in a branch of the Tails repo,

Passing the review stick to anonym for this part.

> on the SKS keyservers, and deployed in our infra

Reviewed the infra side of things, looks good.

> (including http://deb.tails.boum.org/key.asc)

bertagaz, this makes me curious: IIRC I’ve done something semi-recently so that this is automated (at some point a few months ago it was outdated, so I bothered fixing the root cause). Did you have to do anything manual?

#8 Updated by bertagaz 2015-10-28 11:37:56

intrigeri wrote:
> > (including http://deb.tails.boum.org/key.asc)
>
> bertagaz, this makes me curious: IIRC I’ve done something semi-recently so that this is automated (at some point a few months ago it was outdated, so I bothered fixing the root cause). Did you have to do anything manual?

Yep, I had to update the key.asc file in /srv/reprepro/ manually. Didn’t find anything in the manifest about this file, didn’t bother doing that now. I’ll open a ticket to keep that in mind.

#9 Updated by anonym 2015-10-30 05:06:39

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

Applied in changeset commit:1f580012dd6dd092f4735a4b056dcec95c5b0bbd.

#10 Updated by anonym 2015-10-30 05:08:12

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

#11 Updated by anonym 2015-11-03 11:28:41

  • Status changed from Fix committed to Resolved