Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
Knot Resolver
Knot Resolver
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 142
    • Issues 142
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 9
    • Merge Requests 9
  • 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
  • Knot projects
  • Knot ResolverKnot Resolver
  • Issues
  • #233

Closed
Open
Opened Aug 08, 2017 by Vladimír Čunát@vcunatMaintainer

random generator: consider using gnutls instead of ISAAC

GnuTLS _NONCE level might be suitable. TODO: profile.

  • Advantages: smaller state (~2kB -> 140B), dropping extra code that we don't (want to) maintain in exchange for the lib that we depend on anyway, maybe better quality of randomness.
  • Disadvantages: probably more CPU-intensive, but most likely not noticeable for our use cases.
Edited Aug 08, 2017 by Vladimír Čunát
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
2018 Q3
Milestone
2018 Q3 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: knot/knot-resolver#233