diff options
| author | Peter Eisentraut <peter@eisentraut.org> | 2022-09-13 16:10:50 +0200 |
|---|---|---|
| committer | Peter Eisentraut <peter@eisentraut.org> | 2022-09-13 16:10:50 +0200 |
| commit | 257eb57b50f7c65467bfc2f4d579622fa13f3370 (patch) | |
| tree | 74fe36325c4c07f18fba7f6906dc1ef442088bab /src/backend/tcop/postgres.c | |
| parent | 45b1a67a0fcb3f1588df596431871de4c93cb76f (diff) | |
| download | postgresql-257eb57b50f7c65467bfc2f4d579622fa13f3370.tar.gz postgresql-257eb57b50f7c65467bfc2f4d579622fa13f3370.zip | |
Don't reflect unescaped cert data to the logs
Commit 3a0e385048 introduced a new path for unauthenticated bytes from
the client certificate to be printed unescaped to the logs. There are a
handful of these already, but it doesn't make sense to keep making the
problem worse. \x-escape any unprintable bytes.
The test case introduces a revoked UTF-8 certificate. This requires the
addition of the `-utf8` flag to `openssl req`. Since the existing
certificates all use an ASCII subset, this won't modify the existing
certificates' subjects if/when they get regenerated; this was verified
experimentally with
$ make sslfiles-clean
$ make sslfiles
Unfortunately the test can't be run in the CI yet due to a test timing
issue; see 55828a6b60.
Author: Jacob Champion <jchampion@timescale.com>
Discussion: https://www.postgresql.org/message-id/CAAWbhmgsvHrH9wLU2kYc3pOi1KSenHSLAHBbCVmmddW6-mc_=w@mail.gmail.com
Diffstat (limited to 'src/backend/tcop/postgres.c')
0 files changed, 0 insertions, 0 deletions