Re: [PATCH v20] GSSAPI encryption support

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Robbie Harwood <rharwood(at)redhat(dot)com>, 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>
Subject: Re: [PATCH v20] GSSAPI encryption support
Date: 2019-04-04 02:01:48
Message-ID: 20190404020148.GD7693@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro HORIGUCHI 2019-04-04 02:03:20 Re: [HACKERS] WAL logging problem in 9.4.3?
Previous Message Amit Langote 2019-04-04 02:01:41 Re: Inadequate executor locking of indexes