| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re: [COMMITTERS] pgsql: Replace PostmasterRandom() with a stronger way of generating ran |
| Date: | 2016-10-18 03:34:52 |
| Message-ID: | 13663.1476761692@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Michael Paquier <michael(dot)paquier(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2016-10-18 08:10:07 | Re: pgsql: Use OpenSSL EVP API for symmetric encryption in pgcrypto. |
| Previous Message | Michael Paquier | 2016-10-18 01:50:09 | Re: Re: [COMMITTERS] pgsql: Replace PostmasterRandom() with a stronger way of generating ran |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2016-10-18 03:48:28 | Re: Add PGDLLEXPORT to PG_FUNCTION_INFO_V1 |
| Previous Message | Michael Paquier | 2016-10-18 03:12:54 | Re: FSM corruption leading to errors |