You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Heikki Linnakangas fe0a0b5993 Replace PostmasterRandom() with a stronger source, second attempt. ... This adds a new routine, pg_strong_random() for generating random bytes, for use in both frontend and backend. At the moment, it's only used in the backend, but the upcoming SCRAM authentication patches need strong random numbers in libpq as well. pg_strong_random() is based on, and replaces, the existing implementation in pgcrypto. It can acquire strong random numbers from a number of sources, depending on what's available: - OpenSSL RAND_bytes(), if built with OpenSSL - On Windows, the native cryptographic functions are used - /dev/urandom Unlike the current pgcrypto function, the source is chosen by configure. That makes it easier to test different implementations, and ensures that we don't accidentally fall back to a less secure implementation, if the primary source fails. All of those methods are quite reliable, it would be pretty surprising for them to fail, so we'd rather find out by failing hard. If no strong random source is available, we fall back to using erand48(), seeded from current timestamp, like PostmasterRandom() was. That isn't cryptographically secure, but allows us to still work on platforms that don't have any of the above stronger sources. Because it's not very secure, the built-in implementation is only used if explicitly requested with --disable-strong-random. This replaces the more complicated Fortuna algorithm we used to have in pgcrypto, which is unfortunate, but all modern platforms have /dev/urandom, so it doesn't seem worth the maintenance effort to keep that. pgcrypto functions that require strong random numbers will be disabled with --disable-strong-random. Original patch by Magnus Hagander, tons of further work by Michael Paquier and me. Discussion: https://www.postgresql.org/message-id/CAB7nPqRy3krN8quR9XujMVVHYtXJ0_60nqgVc6oUk8ygyVkZsA@mail.gmail.com Discussion: https://www.postgresql.org/message-id/CAB7nPqRWkNYRRPJA7-cF+LfroYV10pvjdz6GNvxk-Eee9FypKA@mail.gmail.com		9 years ago
..
backend	Replace PostmasterRandom() with a stronger source, second attempt.	9 years ago
bin	Add max_parallel_workers GUC.	9 years ago
common	Rename "pg_xlog" directory to "pg_wal".	9 years ago
fe_utils	Teach appendShellString() to not quote strings containing "-".	9 years ago
include	Replace PostmasterRandom() with a stronger source, second attempt.	9 years ago
interfaces	libpq: Fix inadvertent change in PQhost() behavior.	9 years ago
makefiles	Provide NO_INSTALLCHECK option for pgxs.	9 years ago
pl	Check that result tupdesc has exactly 1 column in return_next scalar case.	9 years ago
port	Replace PostmasterRandom() with a stronger source, second attempt.	9 years ago
template	Remove "sco" and "unixware" ports.	9 years ago
test	Document recipe for testing compatibility with old Perl.	9 years ago
timezone	More zic cleanup.	9 years ago
tools	Replace PostmasterRandom() with a stronger source, second attempt.	9 years ago
tutorial	…
.gitignore	…
DEVELOPERS	…
Makefile	Install TAP test infrastructure so it's available for extension testing.	9 years ago
Makefile.global.in	Replace PostmasterRandom() with a stronger source, second attempt.	9 years ago
Makefile.shlib	Remove "sco" and "unixware" ports.	9 years ago
bcc32.mak	…
nls-global.mk	…
win32.mak	…