pgsql: Allow root-owned SSL private keys in libpq, not only the backend

Поиск
Список
Период
Сортировка
От Tom Lane
Тема pgsql: Allow root-owned SSL private keys in libpq, not only the backend
Дата
Msg-id E1nOlS5-000KML-Ax@gemulon.postgresql.org
обсуждение исходный текст
Список pgsql-committers
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.

David Steele

Discussion: https://postgr.es/m/f4b7bc55-97ac-9e69-7398-335e212f7743@pgmasters.net

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/a59c79564bdc209a5bc7b02d706f0d7352eb82fa

Modified Files
--------------
src/backend/libpq/be-secure-common.c     | 28 +++++++++++-----------
src/interfaces/libpq/fe-secure-openssl.c | 40 +++++++++++++++++++++++++++++---
2 files changed, 50 insertions(+), 18 deletions(-)


В списке pgsql-committers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: pgsql: Don't use static storage for SaveTransactionCharacteristics().
Следующее
От: Tom Lane
Дата:
Сообщение: pgsql: Handle integer overflow in interval justification functions.