summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/buffer/buffer.c
diff options
context:
space:
mode:
authorbcook <>2018-12-15 15:10:53 +0000
committerbcook <>2018-12-15 15:10:53 +0000
commita02050f64f180526d478c3b01a391981750865b4 (patch)
tree2a025ce53429b958eef2dca2cf026f2ecfda9eee /src/lib/libcrypto/buffer/buffer.c
parente62c65b7027fd19c83f1f0a8228cea389f0f329d (diff)
downloadopenbsd-a02050f64f180526d478c3b01a391981750865b4.tar.gz
openbsd-a02050f64f180526d478c3b01a391981750865b4.tar.bz2
openbsd-a02050f64f180526d478c3b01a391981750865b4.zip
Backport getentropy changes from deraadt@ on MAIN
Saw a mention somewhere a while back that the gotdata() function in here could creates non-uniformity since very short fetches of 0 would be excluded. blocks of 0 are just as random as any other data, including blocks of 4 4 4.. This is a misguided attempt to identify errors from the entropy churn/gather code doesn't make sense, errors don't happen. ok bcook
Diffstat (limited to 'src/lib/libcrypto/buffer/buffer.c')
0 files changed, 0 insertions, 0 deletions