aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2020-08-04 14:36:09 +0900
committerMichael Paquier <michael@paquier.xyz>2020-08-04 14:36:09 +0900
commit1a01595cc2ffb20ef9f2bc1a92d39728b65e3797 (patch)
treeed37ca876d0e41568c808271cfc19a307ad03ae2
parente7a6cd5dcf24c6d4b04d036a4837c7af154c4b49 (diff)
downloadpostgresql-1a01595cc2ffb20ef9f2bc1a92d39728b65e3797.tar.gz
postgresql-1a01595cc2ffb20ef9f2bc1a92d39728b65e3797.zip
Make new SSL TAP test for channel_binding more robust
The test would fail in an environment including a certificate file in ~/.postgresql/. bdd6e9b fixed a similar failure, and d6e612f introduced the same problem again with a new test. Author: Kyotaro Horiguchi Discussion: https://postgr.es/m/20200804.120033.31225582282178001.horikyota.ntt@gmail.com Backpatch-through: 13
-rw-r--r--src/test/ssl/t/002_scram.pl2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/test/ssl/t/002_scram.pl b/src/test/ssl/t/002_scram.pl
index a1ab9119880..1cdbc50dd3c 100644
--- a/src/test/ssl/t/002_scram.pl
+++ b/src/test/ssl/t/002_scram.pl
@@ -97,7 +97,7 @@ my $client_tmp_key = "ssl/client_scram_tmp.key";
copy("ssl/client.key", $client_tmp_key);
chmod 0600, $client_tmp_key;
test_connect_fails(
- "sslcert=ssl/client.crt sslkey=$client_tmp_key hostaddr=$SERVERHOSTADDR",
+ "sslcert=ssl/client.crt sslkey=$client_tmp_key sslrootcert=invalid hostaddr=$SERVERHOSTADDR",
"dbname=certdb user=ssltestuser channel_binding=require",
qr/channel binding required, but server authenticated client without channel binding/,
"Cert authentication and channel_binding=require");