CLJS-2386 random-uuid should use a cryptographically strong PRNG if a…#317
Open
swannodette wants to merge 1 commit into
Open
CLJS-2386 random-uuid should use a cryptographically strong PRNG if a…#317swannodette wants to merge 1 commit into
swannodette wants to merge 1 commit into
Conversation
…vailable Using cryptographically strong PRNG in most cases closes the gap to the implementation in Clojure where the implementation always uses a cryptographically strong PRNG. Practical exploitation of Math.random predictability on V8 is known. Most modern platforms have a randomUUID method, however this works only in a secure context. The getRandomValues method works as a secure fallback. If none of that works, the Math.random based is used as a last resort. Dereferencing the internal uuid-gen-method unveils the uuid generation strategy.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.