Forbid gen_random_uuid() with --disable-strong-random
Previously, gen_random_uuid() would fall back to a weak random number generator, unlike gen_random_bytes() which would just fail. And this was not made very clear in the docs. For consistency, also make gen_random_uuid() fail outright, if compiled with --disable-strong-random. Re-word the error message you get with --disable-strong-random. It is also used by pgp functions that require random salts, and now also gen_random_uuid(). Reported by Radek Slupik. Discussion: https://www.postgresql.org/message-id/20170101232054.10135.50528@wrigleys.postgresql.org
Showing
- contrib/pgcrypto/expected/pgp-compression_1.out 4 additions, 4 deletionscontrib/pgcrypto/expected/pgp-compression_1.out
- contrib/pgcrypto/expected/pgp-decrypt_1.out 2 additions, 2 deletionscontrib/pgcrypto/expected/pgp-decrypt_1.out
- contrib/pgcrypto/expected/pgp-encrypt_1.out 23 additions, 23 deletionscontrib/pgcrypto/expected/pgp-encrypt_1.out
- contrib/pgcrypto/expected/pgp-pubkey-encrypt_1.out 6 additions, 6 deletionscontrib/pgcrypto/expected/pgp-pubkey-encrypt_1.out
- contrib/pgcrypto/pgcrypto.c 5 additions, 5 deletionscontrib/pgcrypto/pgcrypto.c
- contrib/pgcrypto/px.c 1 addition, 1 deletioncontrib/pgcrypto/px.c
Please register or sign in to comment