Feature #7675: Persist entropy pool seeds
Have a readable blueprint about randomness in Tails
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.
#1 Updated by bertagaz about 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
#8 Updated by intrigeri almost 3 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 over 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 about 2 years 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.
#14 Updated by bertagaz about 2 years ago
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?
- 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! :)
- 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!