Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #17694

Closed (moved)
(moved)
Open
Created Nov 25, 2015 by teor@teor

Hash PRNG output before use, so that it's not revealed to the network

In a review of prop250, ioerror suggests that we should hash raw random values before revealing them to the network.

https://lists.torproject.org/pipermail/tor-dev/2015-November/009954.html

This avoids an attack similar to the one that broke Dual EC: http://projectbullrun.org/dual-ec/ext-rand.html

I have a patch for this, I need to clean it up to merge cleanly on top of #17686 (moved).

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