Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
bolt
bolt
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 29
    • Issues 29
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 1
    • Merge Requests 1
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • bolt
  • boltbolt
  • Merge Requests
  • !165

Merged
Opened May 08, 2019 by Christian Kellner@gicmoOwner

Make sure keys are generated with the right source of randomness

  • Overview 0
  • Commits 5
  • Pipelines 5
  • Changes 8

Before this change, bolt_get_random_data would fall back if getrandom(2) could not be used. The fallbacks can not ensure we have a good enough source of randomness for key creation. Therefore if we can not use the right source just fail, instead of (maybe) creating weak keys. In reality this should have never happened on a modern enough system, i.e. one that has getrandom(2).

Closes #132 (closed)

Assignee
Assign to
Reviewer
Request review from
0.8
Milestone
0.8
Assign milestone
Time tracking
Reference: bolt/bolt!165
Source branch: rndfail