Remove seeding in random number generator #9535
Merged
+0
−4
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.
This is done for the following reasons:
Code clean-up. From https://secure.php.net/manual/en/function.mt-srand.php:
Re-seeding of a PRNG makes it more predictable. E.g., the
microtime()
which is used for the seeding:Because a PRNG's output sequence is equal for the same seed, the re-seeding could make more predictable not only the output of the
Common::getRandomString()
function modified here, but also subsequent calls ofmt_rand()
, which is currently used also in security-related context (see Using secure random numbers #9473).E.g. (not tested), a user could:
Common::getRandomString()
in https://github.com/piwik/piwik/blob/2.16.0-b2/plugins/Monolog/Handler/WebNotificationHandler.php#L46Note: The only other
rand()/mt_rand()
(re-)seeding is in the "Faker" library in https://github.com/piwik/plugin-VisitorGenerator/blob/1.2.2/libs/Faker/Faker/Generator.php#L137, but it doesn't seem to be used at the moment - see https://github.com/piwik/plugin-VisitorGenerator/blob/1.2.2/libs/Faker/readme.md#seeding-the-generator for its use case.