-
Notifications
You must be signed in to change notification settings - Fork 32
improve random seed to a slightly more random number #9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
berthubert
wants to merge
1
commit into
hilch:master
Choose a base branch
from
berthubert:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I appreciate the problem, and I also value the simplicity. But: on the operating system lending this file its name, there's a non-blocking
/dev/urandom
. That's not POSIX, but quite the same on Linux, FreeBSD, and as far as I know also MacOS, and its various mutations.Is there a strong argument for doing a
gettimeofday
syscall and agetpid
syscall to supply low-quality randomness, rather thanopen
,read
, andclose
to get a good seed?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the key point is "as far as we know". Also this code might be used in places that can't see /dev. The seed is not a secret it just needs to vary a bit. I think this library has chosen to be "something that just works", and then this choice is good enough.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see, though I'd like to point out that one of the common places where this kind of time-based seeding fails short is on booting of embedded devices without RTC. E.g., router turns on, takes (down to few milliseconds) exactly the same time to load initrd, boot kernel, launch admin interface, which launches the "first user setup" routine, which hence always ends up with the same time-based seed. I don't know how PIDs are randomized on such a system.
Now, you'll be right to exclaim "but a few milliseconds is still way much variation in µs!", and you'd be very right. But, fun awaits at least under Linux with userland time functions on platforms that don't have a hardware high-res timer register; in many cases, time gets systick-quantized, even on x86_64.
Hence my caveat: I 100% would merge this, it's indubitably an improvement, but for the cases where a non-varying seed is especially problematic, namely, when someone with the same device can reconstruct the same seed, I'm not sure it's a solution :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi guys,
thank you discussing and supporting this project.
This author did some investigations around that:
https://codingnest.com/generating-random-numbers-using-c-standard-library-the-problems/
It looks like there is not simple way to implement a platform independent solution.
/dev/urandom and gettimeofday would prevent us using the code within MS Windows.