Re: How to ensure that SSPI support (Windows) enabled?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dimitry Markman <dmarkman(at)mathworks(dot)com>
Cc: "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: How to ensure that SSPI support (Windows) enabled?
Date: 2023-05-19 15:26:45
Message-ID: 102259.1684510005@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dimitry Markman <dmarkman(at)mathworks(dot)com> writes:
> I’m looking at config_default.pl file and I can see the line
> gss => undef, # --with-gssapi=<path>
> I was advised to use SSPI API that is built-in (windows) instead of MIT Kerberos
> So what should I set and where to ensure that result PostgreSQL build will support SSPI?

SSPI != GSS. SSPI support is always built in Windows builds, see
win32_port.h:

#define ENABLE_SSPI 1

(Perhaps not the best place for such a thing, but somebody put it there.)

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2023-05-19 15:28:25 Re: Memory leak from ExecutorState context?
Previous Message Tomas Vondra 2023-05-19 15:23:56 Re: Memory leak from ExecutorState context?