@Basil Bourque 2017-06-30 05:23:27

configure fails

At least as of Postgres 10 beta, you can look for configure to fail. If you have not given permission for the strong-random to be omitted (via a configure setting), then Postgres built without strong-random will fail during configure.

To quote the 10 beta doc:

• Add more robust random number generators to be used for cryptographic secure uses (Magnus Hagander, Michael Paquier, Heikki Linnakangas)

If no strong random number generator can be found, configure will fail unless the configure --disable-strong-random is used. However, with this option, pgcrypto functions requiring a strong random number generator will be disabled.

@Kassandry 2017-06-29 05:28:41

--disable-strong-random is a PostgreSQL configuration option available in the ./configure script in the source code. You could check to see if your version of PostgreSQL and the associated contrib modules were built with it by using pg_config --configure and looking to see if that particular flag was passed in as part of the config process. Though as it says in the thread that was linked, no reasonable production platform would use that flag, so odds are that you've got a cryptographically random build.

Related Questions

Sponsored Content

Sponsored Content