Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit a282ee6

Browse filesBrowse files
committed
Remove channel binding requirement from clientcert=verify-full test.
This fails on older OpenSSL versions that lack channel binding support. Since that feature is not essential to this test case, just remove it, instead of complicating matters. Per buildfarm. Jacob Champion Discussion: https://postgr.es/m/fa8dbbb58c20b1d1adf0082769f80d5466eaf485.camel@vmware.com
1 parent 0d46771 commit a282ee6
Copy full SHA for a282ee6

File tree

1 file changed

+2
-2
lines changed
Filter options

1 file changed

+2
-2
lines changed

‎src/test/ssl/t/002_scram.pl

Copy file name to clipboardExpand all lines: src/test/ssl/t/002_scram.pl
+2-2Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -104,8 +104,8 @@
104104

105105
# Certificate verification at the connection level should still work fine.
106106
$node->connect_ok(
107-
"sslcert=ssl/client.crt sslkey=$client_tmp_key sslrootcert=invalid hostaddr=$SERVERHOSTADDR dbname=verifydb user=ssltestuser channel_binding=require",
108-
"SCRAM with clientcert=verify-full and channel_binding=require",
107+
"sslcert=ssl/client.crt sslkey=$client_tmp_key sslrootcert=invalid hostaddr=$SERVERHOSTADDR dbname=verifydb user=ssltestuser",
108+
"SCRAM with clientcert=verify-full",
109109
log_like => [
110110
qr/connection authenticated: identity="ssltestuser" method=scram-sha-256/
111111
]);

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.