#golang math/random should work the same as crypto/random if no seed has been given. It being deterministic, but having the same interface as crypto/random is a recipe for failure. Especially with imports now being automatically managed by IDEs, not by developers.
-
-
I think it would be wise to withheld the choice of using a RNG in a security context. E.g. foo.gen_nonce() instead of nonce = unsecure_import.rand(). That would also solve the IDE problem to a degree.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.