Feature #10012
Update our OpenPGP keys in 2015
Start date:
2015-08-14
Due date:
% Done:
100%
Description
What we’re supposed to do each year:
- Add a “Tails developers <tails@boum.org>” UID without comment to our signing key: https://www.debian-administration.org/users/dkg/weblog/97
- Bump the signing key’s expiration date by 1 year, that is to next January 11.
- Generate a new signing subkey for each RM, and move it onto their smartcards.
- Shall we generate and split a revocation certificate for our signing key? See proposal in (#7700).
To be done at the CI sprint in September.
Subtasks
Feature #10013: Test that Tails 1.6 can check a UDF signed with both old and new signing subkeys | Rejected | 0 |
|||
Feature #10014: Sign new and updated UDFs with both old and new signing subkeys | Rejected | 0 |
|||
Feature #10016: Include the updated signing key and new subkeys | Resolved | 100 |
|||
Feature #10019: Include the updated signing key and new subkeys | Rejected | 0 |
|||
Feature #10020: Check whether certifications of our signing key expire | Resolved | 100 |
Related issues
Related to Tails - |
Resolved | 2016-07-16 |
History
#1 Updated by bertagaz 2015-09-23 01:23:20
- Target version changed from Tails_1.6 to Tails_1.7
postponing
#2 Updated by bertagaz 2015-09-27 09:09:14
- Assignee changed from bertagaz to anonym
Changing ownership, as the rest of the subtasks for this ticket, now that we have bumped the subkeys expiration, is on the RM plate.
Note that it changes what needs to be done in the next release given we didn’t create new subkeys but only deal with expiration dates.
#3 Updated by intrigeri 2015-09-28 02:01:35
- Status changed from Confirmed to In Progress
#4 Updated by anonym 2015-10-26 16:50:16
- Status changed from In Progress to Fix committed
- Assignee deleted (
anonym) - QA Check set to Pass
#5 Updated by anonym 2015-11-03 11:30:40
- Status changed from Fix committed to Resolved
#6 Updated by intrigeri 2016-07-16 09:35:38
- related to
Feature #11572: Update our OpenPGP keys in 2016 added