aboutsummaryrefslogtreecommitdiff
path: root/src/backend/jit/llvm/llvmjit_error.cpp
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2022-03-02 11:57:02 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2022-03-02 11:57:02 -0500
commit72918ea86cb9308dd4748b4e269e3a53917cbdca (patch)
tree930bec9935402eebab1f725e76f480a537253ce0 /src/backend/jit/llvm/llvmjit_error.cpp
parent0f7b62f29d16c771486418f88473ce07b605bb92 (diff)
downloadpostgresql-72918ea86cb9308dd4748b4e269e3a53917cbdca.tar.gz
postgresql-72918ea86cb9308dd4748b4e269e3a53917cbdca.zip
Allow root-owned SSL private keys in libpq, not only the backend.
This change makes libpq apply the same private-key-file ownership and permissions checks that we have used in the backend since commit 9a83564c5. Namely, that the private key can be owned by either the current user or root (with different file permissions allowed in the two cases). This allows system-wide management of key files, which is just as sensible on the client side as the server, particularly when the client is itself some application daemon. Sync the comments about this between libpq and the backend, too. Back-patch of a59c79564 and 50f03473e into all supported branches. David Steele Discussion: https://postgr.es/m/f4b7bc55-97ac-9e69-7398-335e212f7743@pgmasters.net
Diffstat (limited to 'src/backend/jit/llvm/llvmjit_error.cpp')
0 files changed, 0 insertions, 0 deletions