From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Jade Koskela <jkoskeladev(at)gmail(dot)com> |
Cc: | PostgreSQL mailing lists <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: SSPI support |
Date: | 2014-07-26 06:46:17 |
Message-ID: | CAB7nPqQubBfRReTXSNmkzVX+ibptpJ738VTEWCTy4pZ1qFDG7Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
On Fri, Jul 25, 2014 at 4:38 PM, Jade Koskela <jkoskeladev(at)gmail(dot)com> wrote:
> What is the support for sspi connections?
SSPI is supported.
> I am seeing a crash in the latest release of the driver on PC.
> The build from the repository doesn't reproduce, it seems there was a patch
> last month.
Yes, there is a fix in this area with this commit:
commit: 41993dbed1308c019a6e14152adf75162b3386fe
author: Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp>
date: Tue, 24 Jun 2014 12:22:15 +0900
This patch fixes a NULL pointer dereference occurring when connecting
using SSPI authentication (without kerberos, a local Windows user trying
to connect to postgres instance on same host). Patch originally by
Nikhil R Deshpande, 1 line added for safety by me.
I imagine that we would need asap a new release of the driver.
> However, when I run 'test connection' from the Windows ODBC Admin on a DSN,
> it gives a warning that says 'sspi not supported'.
How are your settings on the
> I found an old post (2012) that said sspi was supported in the 64bit
> version. This was a 32 bit build.
> Is that the issue? The connection seem to work, the only problem was the
> warning when testing the connection.
Er, I don't recall that 32 or 64 bit are making a difference in this
case. Perhaps you have been using a custom build that did not have
USE_SSPI set?
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Itnal, Prakash (NSN - IN/Bangalore) | 2014-08-08 09:19:45 | Not received any mail from community |
Previous Message | Jade Koskela | 2014-07-25 16:38:07 | SSPI support |