Re: Removing --disable-strong-random from the code
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Postgres hackers <pgsql-hackers@lists.postgresql.org>, Heikki Linnakangas <hlinnaka@iki.fi>
Date: 2018-12-31T01:00:52Z
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
Commits
-
Remove configure switch --disable-strong-random
- 1707a0d2aa6b 12.0 landed
-
Fix generation of padding message before encrypting Elgamal in pgcrypto
- 962da60591df 10.7 landed
- 2882bab920a4 11.2 landed
- d880b208e5fc 12.0 landed