postgresql/contrib/pgcrypto/expected
Michael Paquier 1707a0d2aa Remove configure switch --disable-strong-random
This removes a portion of infrastructure introduced by fe0a0b5 to allow
compilation of Postgres in environments where no strong random source is
available, meaning that there is no linking to OpenSSL and no
/dev/urandom (Windows having its own CryptoAPI).  No systems shipped
this century lack /dev/urandom, and the buildfarm is actually not
testing this switch at all, so just remove it.  This simplifies
particularly some backend code which included a fallback implementation
using shared memory, and removes a set of alternate regression output
files from pgcrypto.

Author: Michael Paquier
Reviewed-by: Tom Lane
Discussion: https://postgr.es/m/20181230063219.GG608@paquier.xyz
2019-01-01 20:05:51 +09:00
..
3des.out
blowfish.out
cast5.out
crypt-blowfish.out
crypt-des.out
crypt-md5.out
crypt-xdes.out
des.out
hmac-md5.out
hmac-sha1.out
init.out
md5.out
pgp-armor.out
pgp-compression.out
pgp-decrypt.out
pgp-encrypt.out
pgp-info.out
pgp-pubkey-decrypt.out
pgp-pubkey-encrypt.out Ooops, missed that a couple of contrib modules have calls to byteacmp. 2009-08-04 18:49:50 +00:00
pgp-zlib-DISABLED.out
rijndael.out pgcrypto's encrypt() supports AES-128, AES-192, and AES-256 2018-01-31 16:33:11 -05:00
sha1.out
sha2.out