Some of the test cases added by commit 3a0e38504 are failing
intermittently in CI testing. It looks like, when a connection
attempt fails, it's possible for psql to exit and the test script
to slurp up the postmaster's log file before the connected backend
has managed to write the log entry we're expecting to see.
It's not clear whether that's fixable in any robust way. Pending
more thought, just comment out the log_like checks. The ones in
connect_ok tests should be fine, since surely the log entry should
be emitted before we complete the client auth sequence. I took
out all the ones in connect_fails tests though.
Discussion: https://postgr.es/m/E1oCNLk-000LCH-Af@gemulon.postgresql.org
# temporarily(?) skip this check due to timing issue
qr{Client certificate verification failed at depth 0: certificate revoked},
# log_like => [
qr{Failed certificate data \(unverified\): subject "/CN=ssltestuser", serial number 2315134995201656577, issuer "/CN=Test CA for PostgreSQL SSL regression test client certs"},
# qr{Client certificate verification failed at depth 0: certificate revoked},
],
# qr{Failed certificate data \(unverified\): subject "/CN=ssltestuser", serial number 2315134995201656577, issuer "/CN=Test CA for PostgreSQL SSL regression test client certs"},
# ],
# revoked certificates should not authenticate the user
# revoked certificates should not authenticate the user
# temporarily(?) skip this check due to timing issue
qr{Client certificate verification failed at depth 0: unable to get local issuer certificate},
# log_like => [
qr{Failed certificate data \(unverified\): subject "\.\.\./CN=ssl-123456789012345678901234567890123456789012345678901234567890", serial number 2315418733629425152, issuer "/CN=Test CA for PostgreSQL SSL regression test client certs"},
# qr{Client certificate verification failed at depth 0: unable to get local issuer certificate},
]);
# qr{Failed certificate data \(unverified\): subject "\.\.\./CN=ssl-123456789012345678901234567890123456789012345678901234567890", serial number 2315418733629425152, issuer "/CN=Test CA for PostgreSQL SSL regression test client certs"},
# ]
);
# Use an invalid cafile here so that the next test won't be able to verify the
# Use an invalid cafile here so that the next test won't be able to verify the
# temporarily(?) skip this check due to timing issue
qr{Client certificate verification failed at depth 1: unable to get local issuer certificate},
# log_like => [
qr{Failed certificate data \(unverified\): subject "/CN=Test CA for PostgreSQL SSL regression test client certs", serial number 2315134995201656577, issuer "/CN=Test root CA for PostgreSQL SSL regression test suite"},
# qr{Client certificate verification failed at depth 1: unable to get local issuer certificate},
]);
# qr{Failed certificate data \(unverified\): subject "/CN=Test CA for PostgreSQL SSL regression test client certs", serial number 2315134995201656577, issuer "/CN=Test root CA for PostgreSQL SSL regression test suite"},
# ]
);
# test server-side CRL directory
# test server-side CRL directory
switch_server_cert(
switch_server_cert(
@ -776,9 +783,11 @@ $node->connect_fails(
.sslkey('client-revoked.key'),
.sslkey('client-revoked.key'),
"certificate authorization fails with revoked client cert with server-side CRL directory",
"certificate authorization fails with revoked client cert with server-side CRL directory",
# temporarily(?) skip this check due to timing issue
qr{Client certificate verification failed at depth 0: certificate revoked},
# log_like => [
qr{Failed certificate data \(unverified\): subject "/CN=ssltestuser", serial number 2315134995201656577, issuer "/CN=Test CA for PostgreSQL SSL regression test client certs"},
# qr{Client certificate verification failed at depth 0: certificate revoked},
]);
# qr{Failed certificate data \(unverified\): subject "/CN=ssltestuser", serial number 2315134995201656577, issuer "/CN=Test CA for PostgreSQL SSL regression test client certs"},