Re: Removing --disable-strong-random from the code

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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-31 01:00:52
Message-ID: 20181231010052.GA4522@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Dec 30, 2018 at 11:56:48AM -0500, Tom Lane wrote:
> 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>

Okay, I have included something among those lines.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2018-12-31 01:20:28 Re: Removing --disable-strong-random from the code
Previous Message Ian Barwick 2018-12-31 00:50:29 Re: Minor comment fix for pg_config_manual.h