pgsql: Implement channel binding tls-server-end-point for SCRAM - Mailing list pgsql-committers

From Peter Eisentraut
Subject pgsql: Implement channel binding tls-server-end-point for SCRAM
Date
Msg-id E1eXCFl-00009k-0q@gemulon.postgresql.org
Whole thread Raw
Responses Re: pgsql: Implement channel binding tls-server-end-point for SCRAM
Re: pgsql: Implement channel binding tls-server-end-point for SCRAM
List pgsql-committers
Implement channel binding tls-server-end-point for SCRAM

This adds a second standard channel binding type for SCRAM.  It is
mainly intended for third-party clients that cannot implement
tls-unique, for example JDBC.

Author: Michael Paquier <michael.paquier@gmail.com>

Branch
------
master

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

Modified Files
--------------
doc/src/sgml/protocol.sgml               | 17 ++++---
src/backend/libpq/auth-scram.c           | 20 ++++++--
src/backend/libpq/be-secure-openssl.c    | 61 ++++++++++++++++++++++++
src/include/common/scram-common.h        |  1 +
src/include/libpq/libpq-be.h             |  1 +
src/interfaces/libpq/fe-auth-scram.c     | 15 ++++++
src/interfaces/libpq/fe-secure-openssl.c | 80 ++++++++++++++++++++++++++++++++
src/interfaces/libpq/libpq-int.h         |  1 +
src/test/ssl/t/002_scram.pl              |  5 +-
9 files changed, 189 insertions(+), 12 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Fix incorrect computations of length of null bitmap inpageinspe
Next
From: Robert Haas
Date:
Subject: pgsql: Simplify and encapsulate tuple routing support code.