Skip site navigation (1) Skip section navigation (2)

Re: krb_server_keyfile setting doesn't work on Windows

From: Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: PG Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: krb_server_keyfile setting doesn't work on Windows
Date: 2009-12-30 23:55:27
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Magnus Hagander wrote:
> 2009/12/30 Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp>:
>> Hi,
>> As far as I tested, the krb_server_keyfile setting
>> in postgres.conf doesn't work on Windows.
>> Because gssapi32.dll(krb5_32.dll) seems to call
>> getenv("KRB5_KTNAME") in msvcr71, postgres.exe
>> should call putenv("KRB5_KTNAME=...") in msvcr71.
>> The attached patch fixes the problem in my test
>> case.
> Isn't the main backend linked with msvcr71.dll anyway?

What main backend directly links is msvcr80 or msvcr90
according to the msvc build environment.

> Then the
> regular putenv should put it in th eenv of  msvcr71.dll, and the stuff
> that's wrapped through src/port/win32env.c will put it in the regular
> msvcr file.
> I wonder if you're possibly being hit with the bug I patched the other
> day, but didn't backpatch.
> (;a=commitdiff;h=f8bcd7220b1166f7c037ceaf0a53958cbc6a7630).
> Can you see if that fix solves your problem as well? (Either directly
> or by testing HEAD)

I'm testing using the current cvs.

> If not, the fix should still go in win32env.c, not directly in auth.c

I don't object to it. Possibly we would have to add msvcr80 or
  msvcr90 as well in the future.

Hiroshi Inoue

In response to


pgsql-hackers by date

Next:From: Magnus HaganderDate: 2009-12-30 23:57:55
Subject: Re: krb_server_keyfile setting doesn't work on Windows
Previous:From: Andres FreundDate: 2009-12-30 23:43:52
Subject: Re: Hot Standy introduced problem with query cancel behavior

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group