| From: | Richard Crampton <rich(dot)crampton(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #16897: gssenc request slow connection |
| Date: | 2021-02-25 20:00:05 |
| Message-ID: | CAL_nAvWANswo64b-e+gXJphzdccaQfPyhBcZbPchb5K73j39vQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
It's not enabled in my pg_hba.conf which I've attached...
On Thu, 25 Feb 2021 at 19:29, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Stephen Frost <sfrost(at)snowman(dot)net> writes:
> > What's the version of the libpq library on the client side..? In
> > general, while there's an extra packet back and forth because Kerberos /
> > GSSAPI is set up on the client / Windows side, once the server says it
> > doesn't support GSSENC, libpq should try a non-GSSENC connection right
> > away..
>
> I'm wondering if the server DOES say it supports GSSENC, and the delay
> is involved in the two sides not realizing they aren't talking to the
> same Kerberos/AD servers, or something like that.
>
> regards, tom lane
>
| Attachment | Content-Type | Size |
|---|---|---|
| pg_hba.conf.txt | text/plain | 4.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-02-25 20:24:09 | Re: BUG #16897: gssenc request slow connection |
| Previous Message | Tom Lane | 2021-02-25 19:29:17 | Re: BUG #16897: gssenc request slow connection |