| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, David Steele <david(at)pgmasters(dot)net>, Joe Conway <mail(at)joeconway(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Nico Williams <nico(at)cryptonector(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Robbie Harwood <rharwood(at)redhat(dot)com> |
| Subject: | Re: [PATCH v20] GSSAPI encryption support |
| Date: | 2019-04-04 02:09:54 |
| Message-ID: | CAOuzzgqS-CL18_zKF7pF-wymG8mUeUZveNYYSrXKQRn1VaJsug@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Greetings,
On Wed, Apr 3, 2019 at 22:02 Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> On Wed, Apr 03, 2019 at 05:51:06PM -0400, Stephen Frost wrote:
> > Thanks so much for pushing on it for so long, it’s a great feature to
> have!
>
> Glad to see that the final result is using an API layer in
> be-secure.c and that we have tests. Now, shouldn't there be some
> documentation in protocol.sgml for the read and write handling of the
> encrypted messages? Other drivers could need to implement that stuff,
> no? We have that for SSL, with SSLRequest and such.
Yes, that’s a fair point. I’ll work on adding documentation to
protocol.sgml for the GSSAPI encrypted setup and message passing.
Thanks,
Stephen
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2019-04-04 02:13:10 | Re: Inadequate executor locking of indexes |
| Previous Message | Michael Paquier | 2019-04-04 02:06:05 | Re: allow online change primary_conninfo |