Re: [ODBC] Re: Connection failure with invalid connection option"gsslib" for 09.06.0410 - Mailing list pgsql-odbc

From Inoue, Hiroshi
Subject Re: [ODBC] Re: Connection failure with invalid connection option"gsslib" for 09.06.0410
Date
Msg-id 200cc17f-0a89-06fd-3fa1-a9db79696c33@dream.email.ne.jp
Whole thread Raw
In response to Re: [ODBC] Re: Connection failure with invalid connection option"gsslib" for 09.06.0410  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: [ODBC] Re: Connection failure with invalid connection option"gsslib" for 09.06.0410  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-odbc
Hi Michael,

On 2017/08/25 22:02, Michael Paquier wrote:
> On Fri, Aug 25, 2017 at 7:34 AM, John Kew <jkew@tableau.com> wrote:
>> Thanks Hiroshi;
> Top-posting is not the recommended way of posting on those mailing lists.
>
>> We can update our mirror and run through our linux tests and it is entirely
>> possible I'm looking in the wrong place; but it *looks* like the change to
>> connection.c would mean that "gsslib" is not passed to libpq regardless of
>> platform:
> Making this parameter never used in is a bad idea as well. It should
> be conditional. It seems to me that Postgres ODBC should track if
> libpq is compiled with GSS or not, and then allow the parameter to be
> passed down or not.

Honestly I don't like this option.
The option had been meaningless for a long time and I almost forget the
meaning.
Users who want to use gssapi authentication on Windows have used sspi
library.
When libpq on Windows happens to be compiled with GSS and you want to use
the GSS library for gssapi authentication, you can add pqopt option e.g.
;pqopt={gsslib=gssapi}.

regards,
Hiroshi Inoue


regards,
Hiroshi Inoue


pgsql-odbc by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [ODBC] Re: Connection failure with invalid connection option"gsslib" for 09.06.0410
Next
From: Michael Paquier
Date:
Subject: Re: [ODBC] Re: Connection failure with invalid connection option"gsslib" for 09.06.0410