Re: GSSAPI server side on Linux, SSPI client side on Windows
От | Brian Crowell |
---|---|
Тема | Re: GSSAPI server side on Linux, SSPI client side on Windows |
Дата | |
Msg-id | CAAQkdDqYiQOfEzb5M4fh054MWhEY77rdLnOAgY2QdS5+QZt-YA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: GSSAPI server side on Linux, SSPI client side on Windows (Christian Ullrich <chris@chrullrich.net>) |
Ответы |
Re: GSSAPI server side on Linux, SSPI client side on Windows
|
Список | pgsql-general |
On Tue, Nov 5, 2013 at 11:35 AM, Christian Ullrich <chris@chrullrich.net> wrote: > Hence my suspicion that it doesn't. I did not have the time to compare every > function call yet. It doesn't. But it's a pretty close match; it looks like it was ported directly from the libpq code. libpq actually uses the same code path for SSPI and GSSAPI on Windows, with a boolean to switch a few things between the two. I've been trying to duplicate those changes in Npgsql. I think I'm getting closer though. I have psql on Windows successfully authenticating, so I can't be too far off. > The GSSAPI error messages are of the usual helpful kind, even including the > colon that is followed by no detail. I've been trying to enable the KRB5_TRACE environment variable in the Postgres child processes, but I can't seem to make it stick. That would (should!) provide some sort of help. —Brian
В списке pgsql-general по дате отправления: