Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #13697

Closed (moved)
Open
Opened 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 admin enable hashed storage. More information
Assignee
Assign to
Tor: unspecified
Milestone
Tor: unspecified
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#13697