Project

General

Profile

Feature #11898

Feature #7675: Persist entropy pool seeds

Have a readable blueprint about randomness in Tails

Added by bertagaz about 1 year ago. Updated 4 months ago.

Status:
In Progress
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
11/04/2016
Due date:
% Done:

10%

QA Check:
Ready for QA
Feature Branch:
Type of work:
Communicate
Blueprint:
Starter:
Affected tool:

Description

We want such kind of document to be ready for outsiders of the team and the encryption community so that they can review the problems we identified regarding randomness and entropy in Tails, and the implementation we plan to make it cryptographically strong enough.

We'll do that in the related blueprint, and the idea is to have it ready for 33C3 so that Tails people attending can catch others and show them.

History

#1 Updated by bertagaz about 1 year ago

Plan is to have everyone assigned to a related ticket to write a note about it, so that we can include it in the blueprint. There already are bits written, but they may need care and updates before being showed to others.

We'll meet half of November to see where we are at, and will finalize the document

#2 Updated by intrigeri about 1 year ago

Maybe this ticket should be assigned to someone who'll make sure that everyone involved does their bits? (I'm warry of tickets with a milestone and no assignee.)

#3 Updated by Dr_Whax about 1 year ago

  • Assignee set to Dr_Whax

Hello watchers!

Please update the blueprint with any information that isn't on it yet. The deadline for this is the 2nd of December.

#4 Updated by anonym 12 months ago

  • Target version changed from Tails_2.9.1 to Tails 2.10

#5 Updated by anonym 11 months ago

  • Target version changed from Tails 2.10 to Tails_2.11

#6 Updated by anonym 9 months ago

  • Target version changed from Tails_2.11 to Tails_2.12

#7 Updated by intrigeri 8 months ago

  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 10
  • Parent task set to #7675

#8 Updated by intrigeri 8 months ago

  • Target version changed from Tails_2.12 to 2017

Apparently setting target version = $nextrelease does not really work, and it clutters the RM view => resetting to the 2017 goal as decided as last summit. Feel free to set a more specific target version that encodes your (realistic) plans better :)

#9 Updated by bertagaz 4 months ago

  • QA Check set to Ready for QA

As discussed on chat, I'm puting this ticket RfQA for Drwhax to review the blueprint. It's in a pretty good shape enough IMO for us to start showing it to our fellow Tails devs for feedbacks, and then external crypto knowledgeable people.

Also available in: Atom PDF