That moment when you use Go math/rand (requires to be seeded, otherwise predictable) instead of crypto/rand, but then you test your own code and find it right away. Remember kids, don't mess it up.
Well Seed(1) is a little more predictable than Seed(epoch) but yes, you are right. The bottom line is to stay away from it for crypto operations ;). I find it too easy to make this mistake given that the invocation of http://rand.Read () is identical...
-
-
I mean, you can reverse it from the outputs. And I'm unhappy about the API collision too.
-
Oh yeah, that’s pretty bad.
End of conversation
New conversation -
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.