You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Commit3a0e385 introduced a new path for unauthenticated bytes fromthe client certificate to be printed unescaped to the logs. There are ahandful of these already, but it doesn't make sense to keep making theproblem worse. \x-escape any unprintable bytes.The test case introduces a revoked UTF-8 certificate. This requires theaddition of the `-utf8` flag to `openssl req`. Since the existingcertificates all use an ASCII subset, this won't modify the existingcertificates' subjects if/when they get regenerated; this was verifiedexperimentally with $ make sslfiles-clean $ make sslfilesUnfortunately the test can't be run in the CI yet due to a test timingissue; see55828a6.Author: Jacob Champion <jchampion@timescale.com>Discussion:https://www.postgresql.org/message-id/CAAWbhmgsvHrH9wLU2kYc3pOi1KSenHSLAHBbCVmmddW6-mc_=w@mail.gmail.com
# temporarily(?) skip this check due to timing issue
803
+
#log_like => [
804
+
#qr{Client certificate verification failed at depth 0: certificate revoked},
805
+
#qr{Failed certificate data \(unverified\): subject "/CN=\\xce\\x9f\\xce\\xb4\\xcf\\x85\\xcf\\x83\\xcf\\x83\\xce\\xad\\xce\\xb1\\xcf\\x82", serial number 2315420958437414144, issuer "/CN=Test CA for PostgreSQL SSL regression test client certs"},