Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • L libotr
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 50
    • Issues 50
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • 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
  • Libraries
  • libotr
  • Issues
  • #101

Closed
Open
Created Apr 01, 2016 by MansourMoufid@mansourmoufid

Use the system PRNG

libgcrypt can generate random numbers in several ways. The first and default is from an internal PRNG, based on the design by Gutmann from 1998, which is seeded at initialization. The second way is using the system PRNG (/dev/random or /dev/urandom). libgcrypt calls the system PRNG "strong" and its own "very strong."

This patch attempts to make libgcrypt use the system PRNG instead of its internal one. I say attempts because there is no easy way to ensure libgcrypt behaves in a certain way.

(from redmine: created on 2015-06-25)

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