From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
Subject: | Re: Removing --disable-strong-random from the code |
Date: | 2018-12-30 16:56:48 |
Message-ID: | 20532.1546189008@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I wrote:
> LGTM otherwise.
Oh, one more thought: the removal of the --disable-strong-random
documentation stanza means there's no explanation of what to do
to build on platforms without /dev/urandom. Perhaps something
like this in installation.sgml:
<para>
- You need <productname>OpenSSL</productname>, if you want to support
- encrypted client connections. The minimum required version is
- 0.9.8.
+ You need <productname>OpenSSL</productname> if you want to support
+ encrypted client connections. <productname>OpenSSL</productname>
+ is also required for random number generation on platforms that
+ do not have <filename>/dev/urandom</filename> (except Windows).
+ The minimum required version is 0.9.8.
</para>
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-12-30 18:24:02 | Is MinMaxExpr really leakproof? |
Previous Message | Tom Lane | 2018-12-30 16:47:03 | Re: Removing --disable-strong-random from the code |