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 937
    • Issues 937
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 27
    • Merge requests 27
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Model experiments
  • 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
  • #6116

Audit random seed

Originally created by Tails on #6116 (Redmine)

See the pkg-sysvinit-devel archives, in July and August 2010, for an interesting discussion about random seeds unicity, especially at early boot time.

We should audit such matters in Tails.

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

Related issues

  • Related to #17154
  • Related to #11897
  • Related to #7102
  • Related to #5650 (closed)
  • Related to #7642 (closed)
  • Related to #7646 (closed)
  • Related to #7675 (closed)
Edited Jul 09, 2020 by intrigeri
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking