Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #23061

Closed (moved)
Open
Opened Jul 31, 2017 by teor@teor

crypto_rand_double() should produce all possible outputs on platforms with 32-bit int

On 32-bit platforms, crypto_rand_double() only produces 1 in every 2 million possible values between 0 and 1.

This happens because:

  • crypto_rand_double() divides a random unsigned int by UINT_MAX
  • an unsigned int on 32-bit platforms is 32 bits
  • the mantissa on a double is 53 bits

So crypto_rand_double() doesn't fill the lower 21 bits with random values.

This makes the rep_hist_format_hs_stats() noise more predictable on 32-bit platforms.

This fix shouldn't affect the unit tests, because they pass on 64-bit.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Tor: unspecified
Milestone
Tor: unspecified
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#23061