Re: [PATCH v18] GSSAPI encryption support

From: Nico Williams <nico(at)cryptonector(dot)com>
To: Robbie Harwood <rharwood(at)redhat(dot)com>
Cc: PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH v18] GSSAPI encryption support
Date: 2018-06-11 23:00:27
Message-ID: 20180611230026.GC23356@localhost
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jun 11, 2018 at 04:11:10PM -0400, Robbie Harwood wrote:
> Nico was kind enough to provide me with some code review. This should
> those concerns (clarify short-read behavior and fixing error checking on
> GSS functions).

Besides the bug you fixed and which I told you about off-list (on IRC,
specifically), I only have some commentary that does not need any
action:

- support for non-Kerberos/default GSS mechanisms

This might require new values for gssmode: prefer-<mechanism-name>
and require-<mechanism-name>. One could always use SPNEGO if there
are multiple mechanisms to choose from. And indeed, you could just
use SPNEGO if the user has credentials for multiple mechanism.

(Because GSS has no standard mechanism _names_, this means making
some up. This is one obnoxious shortcoming of the GSS-API...)

- when the SCRAM channel binding work is done, it might be good to add
an option for TLS + GSS w/ channel binding to TLS and no gss wrap
tokens

Nico
--

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2018-06-11 23:05:04 Re: why partition pruning doesn't work?
Previous Message Andrew Dunstan 2018-06-11 22:41:20 Re: why partition pruning doesn't work?