Bug #16850

Test suite: switch to another testing OpenPGP key

Added by intrigeri about 6 years ago. Updated about 6 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Test suite
Target version:
Tails_3.16
Start date:
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

dkg’s key was attacked and chances are that our scenarios, that use it, are affected. We probably need to switch to another key.

Subtasks

Related issues

Blocks Tails - Feature #16209: Core work: Foundations Team Confirmed

History

#1 Updated by intrigeri about 6 years ago

#2 Updated by segfault about 6 years ago

intrigeri wrote:
> dkg’s key was attacked and chances are that our scenarios, that use it, are affected. We probably need to switch to another key.

We’re not affected, because we don’t use the attacked key (0xc4bc2ddb38cce96485ebe9c2f20691179038e5c6). We use dkg’s old key (0x0ee5be979282d80b9f7540f1ccd2ed94d21739e9). He switched keys in January 2019 (https://dkg.fifthhorseman.net/blog/2019-dkg-openpgp-transition.html).

The old key is expired since 2019-06-29, but the tests we use it for don’t require the key to be valid, so I don’t see a need to switch to another key.

#3 Updated by intrigeri about 6 years ago

  • Status changed from Confirmed to Rejected

Thanks, @segfault!