Project

General

Profile

Feature #11898

Feature #7675: Persist entropy pool seeds

Have a readable blueprint about randomness in Tails

Added by bertagaz almost 3 years ago. Updated about 1 month ago.

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

70%

Feature Branch:
Type of work:
Communicate
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.


Related issues

Related to Tails - Feature #8578: Point friendly academic people to research projects that would help Tails In Progress 01/07/2015
Related to Tails - Feature #7642: Investigate whether we should resume shipping a static random seed Resolved 09/02/2016
Related to Tails - Feature #7102: Evaluate how safe haveged is in a virtualized environment Confirmed 04/17/2014

History

#1 Updated by bertagaz almost 3 years 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 almost 3 years 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 almost 3 years 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 almost 3 years ago

  • Target version changed from Tails_2.9.1 to Tails 2.10

#5 Updated by anonym over 2 years ago

  • Target version changed from Tails 2.10 to Tails_2.11

#6 Updated by anonym over 2 years ago

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

#7 Updated by intrigeri over 2 years ago

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

#8 Updated by intrigeri over 2 years 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 about 2 years 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.

#10 Updated by u over 1 year ago

  • Target version changed from 2017 to 2018
  • Blueprint set to https://tails.boum.org/blueprint/randomness_seeding/

2017 is over.

DrWhax: this ticket is asking for review of the blueprint. Once done with the review, we can continue to work on this and ask for review on tails-dev / external crypto people.

#11 Updated by u over 1 year ago

Do you still plan to work on this? Otherwise please either try to find somebody else to do the review or unassign yourself -> reassign to bertagaz.

#12 Updated by u over 1 year ago

  • % Done changed from 10 to 70

#13 Updated by Dr_Whax over 1 year ago

There's 2 points remaining to add to the blueprint (including some data points). Almost there.

#14 Updated by bertagaz over 1 year ago

Dr_Whax wrote:

There's 2 points remaining to add to the blueprint (including some data points). Almost there.

If you're talking about the to "XXX:" still in the blueprint, I think we can safely ignore them and proceed on the internal reviewing inside Tails. There are other actionables items in there we can very well start implementing before we get these points. So if that's your only remark, maybe we can close this ticket and send this on tails-dev?

#15 Updated by u about 1 year ago

DrWhax: please send this to tails-dev for comments as suggested by bertagaz. I've done a proofread and made it a bit more readable.

#16 Updated by u about 1 year ago

  • Related to Feature #8578: Point friendly academic people to research projects that would help Tails added

#17 Updated by u about 1 year ago

  • Related to Feature #7642: Investigate whether we should resume shipping a static random seed added

#18 Updated by u about 1 year ago

  • Related to Feature #7102: Evaluate how safe haveged is in a virtualized environment added

#19 Updated by Dr_Whax about 1 year ago

I've sent a RFC to tails-dev.

#20 Updated by intrigeri 11 months ago

  • Target version deleted (2018)

#21 Updated by intrigeri 4 months ago

  • Status changed from In Progress to Needs Validation

#22 Updated by Dr_Whax 2 months ago

  • Assignee deleted (Dr_Whax)

I'm no longer going to work on this.

#23 Updated by intrigeri about 1 month ago

  • Assignee set to intrigeri

#24 Updated by intrigeri about 1 month ago

  • Status changed from Needs Validation to Resolved

As explained on https://lists.autistici.org/message/20190811.150250.42ecbf90.en.html, I think we're now done here. Thanks to everyone who participated! :)

Next steps:

  • Finish discussion on implementation details on #11897, get it ready and ship it.
  • Deal with the "Tails started from ISO in a VM" case: #16971.

Regarding the other proposed solutions on the blueprint: they all need more work, be it research (it's not clear whether they would work at all) or implementation. They don't conflict with what's being done on #11897. So whoever is interested in working on any of these further improvements in the future, feel free to create a dedicated ticket, and see you there!

Also available in: Atom PDF