Re: random(4): use arc4random_ctx_buf() for large device reads

On Mon, May 25, 2020 at 05:27:37PM +0200, Christian Weisgerber wrote: > Sebastien Marie: > > > > For large reads from /dev/random, use the arc4random_ctx_*() functions > > > instead of hand-rolling the same code to set up a temporary ChaCha > > > instance. > > > > Eventually, I would get ride of

Re: random(4): use arc4random_ctx_buf() for large device reads

Sebastien Marie: > > For large reads from /dev/random, use the arc4random_ctx_*() functions > > instead of hand-rolling the same code to set up a temporary ChaCha > > instance. > > Eventually, I would get ride of myctx, initialize lctx to NULL, and use > (lctx == NULL) to replace (myctx == 0). R

Re: random(4): use arc4random_ctx_buf() for large device reads

On Sun, May 24, 2020 at 09:33:27PM +0200, Christian Weisgerber wrote: > (This is in a different part of the file from Theo's current efforts.) > > For large reads from /dev/random, use the arc4random_ctx_*() functions > instead of hand-rolling the same code to set up a temporary ChaCha > instance.

Re: random(4): use arc4random_ctx_buf() for large device reads

Makes sense to me. Christian Weisgerber wrote: > (This is in a different part of the file from Theo's current efforts.) > > For large reads from /dev/random, use the arc4random_ctx_*() functions > instead of hand-rolling the same code to set up a temporary ChaCha > instance. > > ok? > > > I

random(4): use arc4random_ctx_buf() for large device reads

(This is in a different part of the file from Theo's current efforts.) For large reads from /dev/random, use the arc4random_ctx_*() functions instead of hand-rolling the same code to set up a temporary ChaCha instance. ok? Index: rnd.c ===

arc4random.3: no more slow random(4) devices

The expensive random(4) devices referred to don't exist any longer and aren't described in that man page, but it's probably worth mentioning how arc4random(3) is different from rand(3) etc. Index: arc4random.3 === RCS

Re: random.4

o say "the same as X". your HISTORY note might still be appropriate though. jmc > Index: random.4 > =========== > RCS file: /home/tedu/cvs/src/share/man/man4/random.4,v > retrieving revision 1.22 > diff -u -r1.

Re: random.4

y need to tell people about one, right? > > > > if you are going to leave the MLINKS for srandom and urandom, i think > you should not kill the stuff, and instead say that they are the same as > whatever you've changed it to. > > otherwise kill the MLIN

Re: random.4

to leave the MLINKS for srandom and urandom, i think you should not kill the stuff, and instead say that they are the same as whatever you've changed it to. otherwise kill the MLINKS. jmc > Index: random.4 > === > RCS file

random.4

Is this the best way to deprecate support for the srandom and urandom devices? The devices themselves are going to stick around for a while, but we only need to tell people about one, right? Index: random.4 === RCS file: /home

random(4) clarifications (was: How to use /dev/srandom)

ys the right choice. This does not attempt to explain *why* arandom(4) continues to output high-quality data even when the entropy pool runs low (the reasons, (pseudorandom) "generator" and "simultaneous", *are* named); I couldn't think of a few to express it concisely enough for a man