| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Robbie Harwood <rharwood(at)redhat(dot)com>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: weird libpq GSSAPI comment |
| Date: | 2020-01-06 21:38:17 |
| Message-ID: | 20200106213817.GA29411@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-Jan-06, Stephen Frost wrote:
> > I wonder if part of the confusion might be due to the synonyms we're
> > using here for "in use". Things seem to be "got running", "set up",
> > "operating", "negotiated", ... - maybe that's part of the barrier to
> > understanding?
>
> How about something like this?
>
> * If GSSAPI Encryption is enabled, then call pg_GSS_have_cred_cache()
> * which will return true if we can acquire credentials (and give us a
> * handle to use in conn->gcred), and then send a packet to the server
> * asking for GSSAPI Encryption (and skip past SSL negotiation and
> * regular startup below).
WFM. (I'm not sure why you uppercase Encryption, though.)
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2020-01-06 21:41:45 | Re: weird libpq GSSAPI comment |
| Previous Message | Andrew Dunstan | 2020-01-06 21:34:34 | Re: jsonb_set() strictness considered harmful to data |