Re:Go 1.11 Beta 1 is released
by staticassertion on Wednesday June 27, 2018 @01:16AM
(#17405934)
Why would it do it randomly then? Just read in the extra byte if you want extra entropy.
[ Parent
| on HN ]
Starting at the link above, click on the #21915 in the commit message, which takes you to https://golang.org/issue/21915.
Re:Go 1.11 Beta 1 is released
by staticassertion on Wednesday June 27, 2018 @01:46AM
(#17406023)
So for no reason, it is about forcing code not to rely on the behavior.
There's a reason given.
Re:Go 1.11 Beta 1 is released
by staticassertion on Wednesday June 27, 2018 @01:44PM
(#17410193)
As in, the reason has nothing to do with entropy, and it is just about breaking code relying on an unspecified behavior.
Re:Go 1.11 Beta 1 is released
by omarforgotpwd on Wednesday June 27, 2018 @02:21PM
(#17410506)
One really easy way to break any encryption scheme is to crack the random number generator. This works because random number generators are deterministic and you can get them to output the exact same stream of random numbers as they did before if you have the same seed / state. This is presumably about making the output of the random number generator harder to predict.
Re:Go 1.11 Beta 1 is released
by staticassertion on Wednesday June 27, 2018 @08:25PM
(#17413080)
> This is presumably about making the output of the random number generator harder to predict.
Randomly deciding to add an extra byte of entropy only adds 1 bit of entropy. Adding the extra byte always adds 8 bits of entropy.
There is no cryptographic reason to do this. It is just to break assumptions about the API.