Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 966
    • Issues 966
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 29
    • Merge requests 29
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #11758
Closed
Open
Issue created Sep 03, 2016 by sycamoreone@sycamoreone

Analyze early boot entropy gathering

Originally created by @sycamoreone on #11758 (Redmine)

One possibility to deal with the missing random seed would be to wait during the boot procedure until enough entropy has been gathered. We need to find out if that is actually possible and what consequences it would have.

Blueprint: https://tails.boum.org/blueprint/randomness_seeding/

Parent Task: #7642 (closed)

Related issues

  • Related to #10779 (closed)
  • Related to #5650 (closed)
Edited May 15, 2020 by sycamoreone
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking