|From:||Stephen Frost <sfrost(at)snowman(dot)net>|
|To:||David CARLIER <devnexen(at)gmail(dot)com>|
|Cc:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>, David Fetter <david(at)fetter(dot)org>, pgsql-hackers(at)postgresql(dot)org|
|Subject:||Re: [PATCH] using arc4random for strong randomness matters.|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
* David CARLIER (devnexen(at)gmail(dot)com) wrote:
> > IIUC, what this code actually does is reseed itself from /dev/urandom
> > every so often and work from a PRNG in between. That's not a layer that
> > we need, because the code on top is already designed to cope with the
> > foibles of /dev/urandom --- or, to the extent it isn't, that's something
> > we have to fix anyway. So it seems like having this optionally in place
> > just reduces what we can assume about the randomness properties of
> > pg_strong_random output, which doesn't seem like a good idea.
> That I admit these are valid points.
Based on the discussion, it looks like this patch should be marked as
'Rejected', so I've gone ahead and done that.
We can reopen it if that's incorrect for some reason.
|Next Message||Michael Paquier||2018-01-12 02:37:22||Re: Enhance pg_stat_wal_receiver view to display connected host|
|Previous Message||Amit Langote||2018-01-12 02:27:11||Re: [Sender Address Forgery]Re: [Sender Address Forgery]Re: [HACKERS] path toward faster partition pruning|