Re: Re: [COMMITTERS] pgsql: Replace PostmasterRandom() with a stronger way of generating ran - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Re: [COMMITTERS] pgsql: Replace PostmasterRandom() with a stronger way of generating ran
Date
Msg-id 13663.1476761692@sss.pgh.pa.us
Whole thread Raw
In response to Re: Re: [COMMITTERS] pgsql: Replace PostmasterRandom() with a stronger way of generating ran  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: Re: [COMMITTERS] pgsql: Replace PostmasterRandom() with a stronger way of generating ran  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
Michael Paquier <michael.paquier@gmail.com> writes:
> And actually, enabling prngd would need to be controlled by a
> configure switch as well disabled by default, no?

AFAICT, openssl has no configuration options related to prngd; they
seem to be able to use it automatically when /dev/[u]random isn't there.
This surprises me a bit because the location of prngd's random-data socket
is evidently variable.  I've not dug into exactly how openssl figures that
out, but I'm sure a little quality time with the openssl sources would
explain it.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: FSM corruption leading to errors
Next
From: Craig Ringer
Date:
Subject: Re: Add PGDLLEXPORT to PG_FUNCTION_INFO_V1