Bug #11380

Write instructions for members of the revocation mechanism

Added by sajolida 2016-04-27 05:48:18 . Updated 2016-08-30 03:14:56 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
Tails_2.6
Start date:
2016-04-27
Due date:
% Done:

0%

Feature Branch:
Type of work:
Communicate
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

People with high responsability will be subscribed to this list, so we need to provide them clear instructions on what to do and what not to do with their share of the revocation certificate.

Subtasks

History

#1 Updated by sajolida 2016-07-16 17:38:28

  • Parent task set to #7700

#2 Updated by sajolida 2016-07-16 17:38:59

  • Assignee deleted (sajolida)
  • Target version set to Tails_2.5
  • QA Check set to Ready for QA

Done in internal:processes/signing_key_revocation.mdwn.

#3 Updated by intrigeri 2016-08-01 07:09:00

  • Assignee set to intrigeri
  • Target version changed from Tails_2.5 to Tails_2.6

#4 Updated by intrigeri 2016-08-11 11:52:13

  • Assignee changed from intrigeri to sajolida
  • QA Check changed from Ready for QA to Dev Needed

I’m not sure what “all the cryptographic keys” refers to in this draft.

Other than that, it looks good to me!

#5 Updated by sajolida 2016-08-30 03:14:56

  • Status changed from Confirmed to Resolved
  • Assignee deleted (sajolida)
  • QA Check deleted (Dev Needed)

Clarified now in ff68dbe. I’m now saying “cryptographic material” instead of “cryptographic keys”.