Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #13697

Closed (moved)
(moved)
Open
Created Nov 07, 2014 by Nick Mathewson@nickm🍬

Carry entropy across invocations

Wen Tor starts, after seeding the CSPRNG, we should save some of its output to an "entropy" file. On later invocations, we should reseed from that file in addition to seeding from the OS, and then replace it with new CSPRNG output.

This is silly voodoo that might help us out if we're ever in a position where the OS has previously been well seeded but later is not. It can't make things worse, so long as RAND_add() is additive.

It's deferrable; #13696 (moved) is more important, assuming a non-broken OS.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking